76
edits
QA/Automation/Projects/Mozmill Automation/Mozmill2Scripts: Difference between revisions
Jump to navigation
Jump to search
QA/Automation/Projects/Mozmill Automation/Mozmill2Scripts (view source)
Revision as of 23:35, 13 March 2012
, 13 March 2012→Proposal
| Line 94: | Line 94: | ||
These methods will offer the same functionality to the consumer, but will be changed to offer support for Mozmill 2. | These methods will offer the same functionality to the consumer, but will be changed to offer support for Mozmill 2. | ||
There will also be | There will also be three new methods: | ||
* get_report | * get_report | ||
* send_report | * send_report(report_url) | ||
* get_mozmill_version | |||
These two methods offers the TestRun the ability to get and send reports since this concept is very different in Mozmill 1.5 and 2.0. | These two reporting methods offers the TestRun the ability to get and send reports since this concept is very different in Mozmill 1.5 and 2.0. | ||
get_mozmill_version will use the Mozmill's metadata to return the version number. This might be useful for classes that inherit TestRun to be able to not run for specific versions. | |||
Another possible feature is to have a constraint "allow_legacy_api" that will prevent systems with the Mozmill 1.5 API to run the tests. | |||
=== Verification === | |||
To verify that the implementation is correctly working for Mozmill 1.5: | |||
# The results of an older TestRun must match the new one for all the current restart and non-restart tests | |||
# Ensure that the results are reported correctly | |||
Likewise, for Mozmill 2.0: | |||
# Results of Mozmill 1.5 API restart and non-restart tests are the same for both Mozmill 2.0 and Mozmill 1.5 | |||
# Ensure that tests using only Mozmill 2.0 API are working | |||
# Ensure that the new features (e.g. screenshot) are working by creating simple tests | |||
# Ensure that the results are reported correctly | |||
==Resources== | ==Resources== | ||