Confirmed users
656
edits
Auto-tools/Projects/Test-Informant: Difference between revisions
Auto-tools/Projects/Test-Informant (view source)
Revision as of 20:55, 16 December 2014
, 16 December 2014→Implementation Details
No edit summary |
|||
| Line 5: | Line 5: | ||
The goal of Test Informant is to provide a higher level of visibility into the current state of our tests. When someone asks questions like "How many reftests are we running on linux64 debug builds?" or "What percentage of mochitests are skipped on android?" we should be able to answer them by directing them towards a Test Informant report. | The goal of Test Informant is to provide a higher level of visibility into the current state of our tests. When someone asks questions like "How many reftests are we running on linux64 debug builds?" or "What percentage of mochitests are skipped on android?" we should be able to answer them by directing them towards a Test Informant report. | ||
= Implementation | = Implementation = | ||
Test informant uses [https://pulse.mozilla.org pulse] to listen for the completion of builds on mozilla-central. It then downloads the tests.zip of the associated build and parses as many test suite manifests as it knows about. It saves the results in a mongo database and continues indefinitely. | Test informant uses [https://pulse.mozilla.org pulse] to listen for the completion of builds on mozilla-central. It then downloads the tests.zip of the associated build and parses as many test suite manifests as it knows about. It saves the results in a mongo database and continues indefinitely. | ||