Add autopilot suite and code coverage gating to autopilot MPs
Bug #1259334 reported by
Francis Ginther
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Services |
New
|
Undecided
|
Francis Ginther |
Bug Description
1) Add the autopilot test suite as a gating test for lp:autopilot MPs.
- Begin with amd64 (and ideally i386) and add touch devices when the suite is ready. The QA team will notify CI when touch is ready to enable.
- Note: we currently only have amd64 systems configured for this type of testing. Enabling tests on i386 is a stretch goal here.
2) Add code coverage as a gating test such that MPs which lower the code coverage are rejected.
1) is more urgent then 2).
To post a comment you must log in.
The commands to generate coverage reports for the autopilot unit tests are as follows:
python -m coverage erase tests.unit
python -m coverage run --branch --include "autopilot/*" -m autopilot.run run autopilot.
python -m coverage xml
The first command erases any existing coverage data. If you're running in a clean environment you don't need this (but it can't hurt).
The second command runs the tests, and generates coverage data in an internal data format.
The third and final command writes a file named 'coverage.xml' in the current directory that jenkins should be able to parse.
Let me know if you need anything else.