QA/Mozmill Test Automation/Shared Modules: Difference between revisions
Jump to navigation
Jump to search
m (→Overview) |
|||
| Line 23: | Line 23: | ||
|- valign="top" | |- valign="top" | ||
| '''Documentation:''' | | '''Documentation:''' | ||
| [https://developer.mozilla.org/en/Mozmill_Tests/Shared_Modules | | [https://developer.mozilla.org/en/Mozmill_Tests/Shared_Modules API documentation] on MDN | ||
|} | |} | ||
Revision as of 19:51, 22 April 2010
Overview
| Lead: | Henrik Skupin |
| Co-workers: | Anthony Hughes |
| Dates: | No end date set |
| Status: | Identifying, creating, and enhancing Shared Modules |
| Repository Location: | http://hg.mozilla.org/qa/mozmill-tests/shared-modules/ |
| Tracking Bug / Bug List: | Shared Module requests |
| Documentation: | API documentation on MDN |
Excerpt
To ease the creation of Mozmill tests for a given subgroup, it's helpful to have a set of helper functions available, which can be called to achieve a wanted action. With the creation of shared modules we want to follow this idea and create function or even classes to simplify the access of single elements or whole dialogs.
Project details
Whenever you want to start to automate a new BFT/FFT subgroup on Litmus, you should first think about having a shared module in place. Creating a list of requirements should be the first step you will have to do as early as possible in the whole process. That will allow us to help you or even write the shared module on our own. Once it has been done, you can start writing Mozmill tests for that subgroup.