canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714
edits
QA/Automation/Projects/TPS: Difference between revisions
Jump to navigation
Jump to search
→System setup
| Line 57: | Line 57: | ||
|} | |} | ||
== | == Documentation == | ||
As of now the [https://github.com/jonallengriffin/coversheet/issues TPS CI] is run via a Python script on Ubuntu only. Also it only runs [https://developer.mozilla.org/en-US/docs/TPS TPS tests] for each check-ins on mozilla-central. Currently each test run takes about 25 minutes. | |||
With our quarterly goal we want to increase the test coverage to support the following: | |||
* Coverage of all desktop platforms: OS X (10.9), Linux (Ubuntu 14.04), and Windows (8.1) | |||
* Coverage of all supported branches: mozilla-central, mozilla-aurora, mozilla-beta, mozilla-release, and mozilla-esr31 (later) | |||
* If necessary system should be expandable to also cover landings on mozilla-inbound | |||
* [https://jenkins-ci.org/ Jenkins] as continuous integration system installed on the master node | |||
* Mozilla Pulse for build broadcasts | |||
Every time when a new build gets pushed to the FTP server, we will receive a message via Mozilla Pulse. Given the configuration only en-US builds will be obeyed for now, but we should be able to extend if requested later. The build information together with the locations for the build binary and the packaged tests will be passed to Jenkins, where a TPS job will be started. Jenkins itself will find a free slave and automatically starts a testrun on that box. Each box might be able to run several testruns in parallel. | |||
== References == | == References == | ||
* TPS: https://developer.mozilla.org/en-US/docs/TPS | * TPS: https://developer.mozilla.org/en-US/docs/TPS | ||
* TPS Tests: https://developer.mozilla.org/en-US/docs/TPS_Tests | * TPS Tests: https://developer.mozilla.org/en-US/docs/TPS_Tests | ||