QA/Desktop Firefox/GetInvolved/Tasks: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 5: Line 5:
'''Mentors:''' Jason Smith
'''Mentors:''' Jason Smith


1. Find a bug you would like to triage here - http://bit.ly/KzIH2Y
# Find a bug you would like to triage here - http://bit.ly/KzIH2Y
2. Open the bug and read the bug carefully
# Open the bug and read the bug carefully
3. Move the bug to a product and component in bugzilla that you think most appropriately maps to the bug description
# Move the bug to a product and component in bugzilla that you think most appropriately maps to the bug description


== Verifying Important Bug Fixes ==
== Verifying Important Bug Fixes ==

Revision as of 22:19, 15 June 2012

Tasks for Contributors

Triage Unconfirmed Bugs

Mentors: Jason Smith

  1. Find a bug you would like to triage here - http://bit.ly/KzIH2Y
  2. Open the bug and read the bug carefully
  3. Move the bug to a product and component in bugzilla that you think most appropriately maps to the bug description

Verifying Important Bug Fixes

Mentors: Jason Smith, Anthony Hughes

  1. Find a bug you would like to verify in this bug query: http://bit.ly/LOGYGE
  2. Carefully read over the bug and make sure you understand what the problem is, the expected results, and the actual results from an end-user's perspective
  3. Try to reproduce the bug on the firefox build where the bug occurred by downloading the firefox build here - ftp://ftp.mozilla.org/pub/firefox/
  4. Test to see if the bug is fixed on each firefox build that the bug is claimed to be fixed. To know what firefox builds you need to verify it, look for the status-firefox fields saying "fixed" and whether the fix was pushed to mozilla central. With mozilla central, you will need to verify the fix on nightly. For others, find the build at ftp://ftp.mozilla.org/pub/firefox/ and verify the fix on the appropriate version of the build
  5. Drop a comment on the bug indicating the results of your testing and cc Jason Smith and Anthony Hughes on the bug
  6. We'll work with you from there to indicate if the bug should be reopened, verified, or needs more testing

Running Mozmill Automated Tests

Mentor: Anthony Hughes (irc: ashughes)

  1. Download and install the latest Firefox Nightly build
  2. Set up the Mozmill command-line client following these instructions
  3. Set up your Mercurial configuration using these instructions
  4. Clone the tests using these instructions
  5. Run the start-l10n script from your MozillaBuild folder
  6. cd to the folder where mozmill-tests was cloned
  7. Run the tests using the following syntax:
mozmill --binary=%path_to_Firefox_build% 
        --test=tests/functional/ 
        --logfile=testrun.log 
        --report=http://mozmill-crowd.blargon7.com/db/

More details about syntax can be found here or by running mozmill --?

Once the tests complete (~15 minutes) your results will appear on the mozmill-crowd dashboard.

If your report contains any failures, please consult the open Mozmill Tests bugs. If there is not a bug on file for a failure you are seeing, please file it in Bugzilla using one of the open bugs as an example.

If you don't have a Bugzilla account, please sign-up for one (all you need is an email address).

If you need help, please join the #automation channel on irc.mozilla.org and ask for help.