canmove, Confirmed users
2,041
edits
Firefox OS/Performance/Automation: Difference between revisions
Jump to navigation
Jump to search
→Overview
| Line 45: | Line 45: | ||
* If performance tests prove untrustworthy, the metric in general will sometimes be written off and even after repair the results may be treated with low priority. | * If performance tests prove untrustworthy, the metric in general will sometimes be written off and even after repair the results may be treated with low priority. | ||
In short, performance tests are a mission-critical system, and require a mission-critical approach. They must be correct, and their behavioral and statistical characteristics need to be well-known. | In short, performance tests are a mission-critical system, and require a mission-critical approach. They must be correct, and their behavioral and statistical characteristics need to be well-known. The consequences of having bad performance tests can be worse than the consequences of having no test at all. | ||
Our workflow is described in a series of deliverables. | Our workflow is described in a series of deliverables to ensure the tests will be good. Reviews for validity and result repeatability are inline with other deliverables to ensure each test brings positive value to Firefox OS. | ||
With only a couple of exceptions, each deliverable depends on the last to be completed before it may be started | With only a couple of exceptions, each deliverable depends on the last to be completed before it may be started. | ||
=== Deliverables === | === Deliverables === | ||