QA/Community/Daily Testing: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
Line 11: Line 11:
**Firefox 2.0 builds: Monday - Friday
**Firefox 2.0 builds: Monday - Friday
*** Windows, Macintosh and/or Linux
*** Windows, Macintosh and/or Linux
*Retrieve the appropriate build when it becomes available. Then go to http://litmus.mozilla.org/ and create a run using the configuration for the build you are testing. Login (create an account if you don't have one) and submit test case results for the smoketests that you run. Use https://bugzilla.mozilla.org to search for or file any bugs you see in the build.  Ideally, we'd like to see the smoketests completed by 10:00 am Pacific Standard Time. But if that is not practical for your schedule, submit results as early as you can.
*Retrieve the appropriate build when it becomes available. Then go to http://litmus.mozilla.org/ and create a run using the configuration for the build you are testing. Login (create an account if you don't have one) and submit test case results for the smoketests that you run. Use https://bugzilla.mozilla.org to search for or file any bugs you see in the build.  Ideally, we'd like to see the bug mentioned and listed in the litmus the Litmus test cases result
*Post to the group email any blocker bugs found.  We'll need to escalate any serious problems in builds that are untestable. Also, if you need help or have questions, ask in irc.mozilla.org #qa.
*Post to the group email any blocker bugs found.  We'll need to escalate any serious problems in builds that are untestable. Also, if you need help or have questions, ask in irc.mozilla.org #qa.
*Check out your results from the links to Litmus searches at http://tbird.tbird.xsmail.com/public/resultslinks.html. I recommend bookmarking that link and setting up its properties to "Load this bookmark in the sidebar"


== '''Rewards''' ==
 
We'd like to show our appreciation for regularly reliable contributors. Specifics haven't been ironed out yet, but the following are likely:
 
*Monthly - Mozilla Store gift certificates to top contributors. (TBD)
*Monthly - Mozilla Store gift certificates for standout contributors. (TBD)
*Outstanding contributor granted Project Lead (as the project expands into multiple areas, we'll need community members to step up and take lead on many of them. We just don't have the numbers at Mozilla to take on everything)
== '''Future Project Items''' ==
== '''Future Project Items''' ==
This list is by all means not complete or set in stone.
This list is by all means not complete or set in stone.

Revision as of 17:50, 7 September 2006

Welcome to the Mozilla QA Community Daily Testing Project

In 2006, one of the highest priorities of Mozilla Quality Assurance is to include interested community members in the daily operations of Mozilla QA.

State of the Project

The project is now open to anyone willing to contribute.

How to Contribute

Follow these basic instructions.

  • Go to http://mail.mozilla.org/listinfo/communityqateam and subscribe to the group email list. This email group is for communication related to the community testing project.
  • Testing schedule as follows:
    Choose builds(s), day(s), and platform(s) to test:
    • Firefox 2.0 builds: Monday - Friday
      • Windows, Macintosh and/or Linux
  • Retrieve the appropriate build when it becomes available. Then go to http://litmus.mozilla.org/ and create a run using the configuration for the build you are testing. Login (create an account if you don't have one) and submit test case results for the smoketests that you run. Use https://bugzilla.mozilla.org to search for or file any bugs you see in the build. Ideally, we'd like to see the bug mentioned and listed in the litmus the Litmus test cases result
  • Post to the group email any blocker bugs found. We'll need to escalate any serious problems in builds that are untestable. Also, if you need help or have questions, ask in irc.mozilla.org #qa.


Future Project Items

This list is by all means not complete or set in stone.