canmove, Confirmed users
2,041
edits
Firefox OS/Performance/Automation: Difference between revisions
Jump to navigation
Jump to search
→Deliverables
| Line 59: | Line 59: | ||
; Results Review : Review by test stakeholders of a set of results of the implemented test. This is a sanity check for whether the results look like something valid (a result frame rate of 70fps on a 60Hz screen would fail this, for example) and whether they are essentially repeatable (reasonably grouped, assuming no code changes). | ; Results Review : Review by test stakeholders of a set of results of the implemented test. This is a sanity check for whether the results look like something valid (a result frame rate of 70fps on a 60Hz screen would fail this, for example) and whether they are essentially repeatable (reasonably grouped, assuming no code changes). | ||
; Published Results : Automated results published to a dashboard or similar display. This usually also implies having an automated triggering and execution mechanism (nightly, on-commit, etc.) to generate them. | ; Published Results : Automated results published to a dashboard or similar display. This usually also implies having an automated triggering and execution mechanism (nightly, on-commit, etc.) to generate them. | ||
; Documentation : Finalized documentation on wiki and/or MDN of the test case and its usage. | ; Documentation : Finalized documentation on this wiki and/or MDN of the test case and its usage. | ||
=== Illustration === | === Illustration === | ||