Confirmed users
14,525
edits
| Line 33: | Line 33: | ||
Once we have nearly finished the BFT testgroup, we will have to check if automating all FFT's is useful or not. | Once we have nearly finished the BFT testgroup, we will have to check if automating all FFT's is useful or not. | ||
== | == Finding a Test to Write == | ||
'''1) Learn how to run Mozmill Tests''' | |||
* If you haven't done so already, you should learn how to [https://developer.mozilla.org/en/Mozmill_Tests#Running_Mozmill_Tests run Mozmill tests] on your own computer. This is a crucial first step in understanding what a Mozmill test is, how it is structured, and how it works. It's also a great point of reference when writing your own tests. | |||
'''2) Check the Milestone''' | |||
* Look above at the ''current milestone''. This will help you identify where we need the most help. Ideally we would like you to help with our current milestone. | |||
'''3) Check the Spreadsheet''' | |||
* Look at our [http://spreadsheets.google.com/ccc?key=pAP5Y5AH3-Tl-wRoNgBujUQ&pli=1 Google spreadsheet] of test automation. Scroll down to find the area matching our ''current milestone''. All Mozmill tests are correlated to a Litmus manual test case. In general, starting from the simplest test is a good idea. | |||
'''4) Still a bit Lost?''' | |||
* If you need help finding a test to work on, feel free to get in contact with the project lead, Anthony, either by [mailto:ahughes@mozilla.com email] or on irc.mozilla.org in the #mozmill channel (nick: ashughes). | |||
* Anthony will help you identify a test, guide you with getting started in test development, and push forward any issues (like Shared Module development) which may prevent you from writing your test; or if he can't he'll find someone who can. | |||
==Filing a Bug== | ==Filing a Bug== | ||