Confirmed users
2,177
edits
QA/Automation/Projects/Endurance Tests/Documentation: Difference between revisions
QA/Automation/Projects/Endurance Tests/Documentation (view source)
Revision as of 20:10, 23 August 2011
, 23 August 2011no edit summary
(Renamed micro-iterations to entities) |
No edit summary |
||
| Line 33: | Line 33: | ||
--no-restart Do not restart application between tests | --no-restart Do not restart application between tests | ||
-r URL, --report=URL Send results to the report server | -r URL, --report=URL Send results to the report server | ||
--reserved=RESERVED Specify a reserved test to run | |||
--repository=URL URL of a custom remote or local repository | --repository=URL URL of a custom remote or local repository | ||
</pre> | </pre> | ||
| Line 47: | Line 48: | ||
=== Reports === | === Reports === | ||
To submit results to a report server, add the <tt>-r URL</tt> or <tt>--report=URL</tt> command line parameter. The preferred target URL for the results is http://mozmill-crowd.brasstacks.mozilla.com/db/ | To submit results to a report server, add the <tt>-r URL</tt> or <tt>--report=URL</tt> command line parameter. The preferred target URL for the results is http://mozmill-crowd.brasstacks.mozilla.com/db/ | ||
=== Reserved Tests === | |||
Reserved tests are any tests that are not to be run in the general endurance testrun. These tests may be to confirm fixes or replicate issues, and may break some of the rules applied to endurance tests. An example of a reserved test that has been checked in is the 'Mem Buster' test, which loads popular websites in separate tabs. The value of this argument must match the target directory name beneath the 'reserved' directory. | |||
= Writing Endurance Tests = | = Writing Endurance Tests = | ||