QA/Automation/Projects/Mozmill Automation/Mozmill2Scripts: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 69: Line 69:
|}
|}


==Proposal (Major changes)==
==Proposal==


=== Inherit from Mozrunner with Mozmill object composition ===
=== Inherit from Mozrunner with Mozmill object composition ===
Line 78: Line 78:


It is possible to inherit from Mozmill API with Mozrunner object composition or use multiple inheritance, but these relationships are less logical. The TestRun module should be a Mozrunner instance logically due to the fact that it handles the preparation and configuration of tests and the Mozilla application. Another reason would be because it helps to be able to override the init in Mozrunner as we do not want to use any of the Mozrunner parser options.
It is possible to inherit from Mozmill API with Mozrunner object composition or use multiple inheritance, but these relationships are less logical. The TestRun module should be a Mozrunner instance logically due to the fact that it handles the preparation and configuration of tests and the Mozilla application. Another reason would be because it helps to be able to override the init in Mozrunner as we do not want to use any of the Mozrunner parser options.
=== Changes to existing methods/new additions ===
The impact of removing Mozmill CLI will affect the following methods within TestRun:
* __init__
** Added: logging capability
* _generate_custom_report
* prepare_binary
* prepare_repository
* prepare_tests
* run_tests
* run
* update_report
These methods will offer the same functionality to the consumer, but will be changed to offer support for Mozmill 2.
There will also be two new methods:
* get_report
* send_report
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.


==Resources==
==Resources==
76

edits

Navigation menu