Engineering Quality Program: Difference between revisions
(→Program Description: added CI goal and changed high level work breakdown into bullets) |
(→Program Description: added release) |
||
| Line 2: | Line 2: | ||
The purpose of the Firefox OS Quality initiative is to drive the engineering team to Continuous Integration through test automation and code coverage, where every commit on Gecko and Gaia triggers a full test run, with failures and performance issues reported on Treeherder for immediate backout. | The purpose of the Firefox OS Quality initiative is to drive the engineering team to Continuous Integration through test automation and code coverage, where every commit on Gecko and Gaia triggers a full test run, with failures and performance issues reported on Treeherder for immediate backout. | ||
The following work must be completed to achieve Continuous Integration: | The following Firefox OS 2.6 work must be completed to achieve Continuous Integration: | ||
* Convert integration tests from GIP to GIJ | * Convert integration tests from GIP to GIJ | ||
* Automate MozTrap scenarios using GIJ when feasible | * Automate MozTrap scenarios using GIJ when feasible | ||
Revision as of 00:32, 3 December 2015
Program Description
The purpose of the Firefox OS Quality initiative is to drive the engineering team to Continuous Integration through test automation and code coverage, where every commit on Gecko and Gaia triggers a full test run, with failures and performance issues reported on Treeherder for immediate backout.
The following Firefox OS 2.6 work must be completed to achieve Continuous Integration:
* Convert integration tests from GIP to GIJ * Automate MozTrap scenarios using GIJ when feasible * Put emulators in place for testing with reporting on Treeherder * Actively maintain working Mulet tests with reporting on Treeherder * Run Marionette.js tests on devices in the Bitbar testing farm with reporting on Treeherder * Run performance tests on devices with reporting on Raptor and Treeherder (Bitbar testing farm) * Create a Test Matrix to define which platform the tests are going to run on (device, mulet, emulator) * Make sure every single commit in gecko/gaia triggers automated tests
Programs and Projects
| Continuous Integration | ||
|---|---|---|
| Marionette Improvements | PM: N/A EPM: Julie McCracken |
ON TARGET |
| GIP to GIJ Conversion | PM: N/A EPM: Julie McCracken |
ON TARGET |
| Test Matrix | PM: N/A EPM: Julie McCracken |
ON TARGET |
| Automated Test Coverage | PM: N/A EPM: Julie McCracken |
ON TARGET |
| Kitkat Emulator Improvements | PM: N/A EPM: Josh Cheng |
ON TARGET |
| Emulator Port | PM: N/A EPM: Josh Cheng |
ON TARGET |
| Raptor Activation on Treeholder | PM: N/A EPM: Bobby Chien |
ON TARGET |
| Release Train Model | ||
| Train Model OTA Branch | PM: N/A EPM: Julie McCracken |
ON TARGET |
| Software Architecture Improvement | ||
| Split BE / FE and apps views | PM: EPM: Maria Oteo |
ON TARGET |
| Mock app BE for FE testing with Telemetry Libraries | PM: EPM: Maria Oteo |
ON TARGET |
| BE tests with Telemetry reports | PM: EPM: Maria Oteo |
ON TARGET |