canmove, Confirmed users
2,041
edits
Line 60: | Line 60: | ||
; Instrumentation : Code either injected into or permanently added to Firefox OS or its applications in order to let automation monitor performance details. Some tests do not need this. | ; Instrumentation : Code either injected into or permanently added to Firefox OS or its applications in order to let automation monitor performance details. Some tests do not need this. | ||
; On-Demand Test : Test that can be run by a developer on command line, try server, or some other way to test a set of arbitrary code. | ; On-Demand Test : Test that can be run by a developer on command line, try server, or some other way to test a set of arbitrary code. | ||
; 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). This is also where we can determine or validate an estimate of test precision, based on real results. | ||
; 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 this 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. |