TPS continuous-integration code should be separate package

RESOLVED FIXED

Status

Testing
TPS
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: jgriffin, Assigned: Sam Garrett)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
This would allow the actual test runner and the tests to be updated automatically on each testrun as needed.

The parts that need to be split into a separate package are the pulse-related code and some new code which could invoke the TPS testrunner as a subprocess.

This new package should not be in m-c, but should probably live on github.
(Reporter)

Comment 1

6 years ago
In keeping with the office space theme, the new automation code will live at https://github.com/jonallengriffin/coversheet.  

Currently, TPS works like this:

1 wait and listen for pulse notification of new build
2 when a notification is received, download the build
3 run the tests

I imagine the new automation bits will work like this:

1 wait and listen for pulse notification of new build
2 when a notification is received, download the build *and* the test package
3 extract the test package, which includes the TPS testrunner and the TPS tests
4 run the tests by invoking the testrunner using subprocess

#3 above is dependent on bug 740227 (currently, TPS is not part of the downloadable test package).
(Reporter)

Comment 2

6 years ago
Sam Garrett has implemented this in https://github.com/jonallengriffin/coversheet, and I've rolled this out on the CI.  I'll file separate bugs if any problems appear with it.
Assignee: nobody → samdgarrett
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Whiteboard: [good first bug][mentor=jgriffin][lang=py]
You need to log in before you can comment on or make changes to this bug.