Releases/Firefox 17/Test Plan

From MozillaWiki
Jump to navigation Jump to search

« Firefox 16 | Firefox 17 | Firefox 18 »

Firefox 17 Test Plan

Summary

Milestone Firefox 17
Status Currently in Aurora -- merging to Beta on October 9, 2012
Lead Anthony Hughes (irc: ashughes)
2nd Juan Becerra (irc: juanb)
Builds [ftp] [http] [web]

The following is the test plan for Firefox 17 from Nightly through to Release. Use this document as a reference for what is being tested to validate the quality of Firefox 17. After the release this document will be used as an archive of what was done to validate this release.

If you have some free time, please pick a task below and get in touch with one of the leads.

Details

The following is a description of the tasks which need to be completed throughout this release.

  • 2012-07-16: {{|}} Nightly Merge
  • 2012-08-27: {{|}} Aurora Merge
  • 2012-10-08: {{|}} Pre-Beta feature sign-offs
  • 2012-10-11: {{|}} Beta 1
  • 2012-10-18: {{|}} Beta 2
  • 2012-10-25: {{|}} Beta 3
  • 2012-11-01: {{|}} Beta 4
  • 2012-11-08: {{|}} Beta 5
  • 2012-11-15: {{|}} Beta 6
  • 2012-11-19: {{|}} Release Candidate
  • 2012-11-20: {{|}} Final

Nightly

Merge

Functional Automation - result
Update Spotchecks - result

Features

See the Feature Release Tracking wiki for a general overview

Features

See the Feature Release Tracking wiki for a general overview

Feature Owner Status Tests
Silent Update: Updated workflow for users with incompatible add-ons Ioana Budnar TBA

Endurance Automation

The purpose of this section is to track any potential memory regressions via spikes reported in the dashboard.

What to Do
  1. Check the Charts
  2. If you see an anomalous event (ie. spike or dip), get the report for the specific event
  3. If the event happens twice in a row, file a bug under Mozmill Tests
  4. Notify Anthony Hughes of the issue
  5. Record the event in this wiki below
Current Status (Mihaela Velimiroviciu) - Last Updated

Bugzilla query error

Query options must be valid JSON.1


Functional Automation

The purpose of this section is to track any potential functional regressions via results reported in the dashboard.

What to Do
  1. Check the testrun reports
  2. If you see any failing tests, check that there are not any bugs on file for it already
  3. If not, file a bug under Mozmill Tests
  4. Notify Anthony Hughes of the issue
  5. Record the event in this wiki below
Current Status (Vlad Maniac / Alex Lakatos) - Last Updated


Bug Triage

The purpose of this section is to triage UNCONFIRMED incoming bugs.

What to Do
  1. Check the UNCONFIRMED bugs
  2. Test the bugs in the latest Firefox Nightly
  3. If you can't reproduce the bug, ask for the reporter to provide more information
  4. If you reproduce the bug, add your testing information and mark the bug NEW
  5. Notify Anthony Hughes of the NEW issue
Current Status (Vlad Ghetiu / Virgil Dicu) - Last Updated

Result Spreadsheet


Aurora Merge Sign-off

NOTE - OSX 10.5 should not be able to install nor update to Firefox 17

Automated Tests

Results of the Mozmill automation testruns.

Functional Tests
Platform Result: report Failures: known bugs
Windows XP result
Windows Vista result
Windows 7 32-bit result
Windows 7 64-bit result
Mac OS X 10.6 result
Mac OS X 10.7 result
Ubuntu 11.10 32-bit result
Ubuntu 11.10 -bit result
Bugs
Endurance Tests
Platform Result: report Max Memory
Windows XP result
Windows Vista result
Windows 7 32-bit result
Windows 7 64-bit result
Mac OS X 10.6 result
Mac OS X 10.7 result
Ubuntu 11.10 32-bit result
Ubuntu 11.10 -bit result
Bugs

Feature Sign-offs

  • Log in to moztrap.mozilla.org
  • Select Run Tests
  • Select Product: Desktop Firefox
  • Select Versions: 17
  • Select Runs: Firefox 17 Aurora Merge Feature sign off
Feature Owner Win32 Mac Linux
Silent Update: Updated workflow for users with incompatible add-ons Ioana Budnar result result result
Details

Report any detailed results or bugs here...