Confirmed users
14,525
edits
| Line 111: | Line 111: | ||
| | | | ||
|- | |- | ||
| | | [[#Test_Refactoring | Test Refactoring]] | ||
| Refactoring | | Refactoring existing tests to use new APIs | ||
| | | [http://bit.ly/t5HWZM mozmill-test-refactor] | ||
| | | 7 Bugs Available | ||
|} | |} | ||
''Prioritized by increasing complexity and decreasing need'' | ''Prioritized by increasing complexity and decreasing need'' | ||
| Line 184: | Line 184: | ||
* Comment in the bug introducing yourself and ask for help getting started | * Comment in the bug introducing yourself and ask for help getting started | ||
* Feel free to [mailto:ahughes@mozilla.com email me directly] if you have any questions | * Feel free to [mailto:ahughes@mozilla.com email me directly] if you have any questions | ||
=== Test Refactoring === | |||
The ''Test Refactoring'' project is about refactoring (changing) the code in existing tests to use current APIs. The Mozmill APIs undergo changes frequently to make tests easier to write, implement new features, or to stabilize the test suite. Some of the tests are well over a year old and need to be updated to these new improvements. This is a great way to learn the structure of tests, the APIs and how they are used. | |||
* | |||
== Contributing == | == Contributing == | ||