Closed Bug 1331993 Opened 7 years ago Closed 4 years ago

run contract tests as part of CI

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

Details

(Whiteboard: [lang=python]) 

Contract tests of the public API were added to Balrog in https://github.com/mozilla/balrog/pull/210. The initial intention is to run these on Cloudops QA infrastructure as part of the deployment process, but it would be good to run them as part of CI as well.

The big difference with running them in CI is that they'll need to query using Flask's TestClient instead of a real web server. This probably also means that they should import a production database dump, so that queries don't always return empty update responses.

It's probably easiest to add a new Task to do this rather than trying to run it as part of the existing backend tests.
Whiteboard: [lang=python]
Priority: -- → P3

This never ended up adding any value and were removed awhile back.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.