Releases/Firefox 37/Test Plan
Summary
This page is to track testing of Firefox 37 from mozilla-central (Nightly) through to mozilla-release. This is intended to be a minimal set of information to help Firefox QA understand and communicate the quality of upcoming releases. Our current walkthrough of the release and QA process will be changing during December 2014.
Schedule
| Milestone | Checks | Due |
| Nightly | Conduct daily stability and bug triage, ensure features are owned | (Release date: 2014-12-01 ) |
| Aurora Migration | Conduct testing to ensure Firefox 34 Aurora builds are okay | (Migration date: 2015-01-12) |
| Aurora | Conduct daily stability and bug triage, ensure features are tested | (Aurora release date: 2015-01-13) |
| Beta | Follow up on stability and verification. | (Release date: 2015-02-24) |
| Release | Firefox 37 release date. | 2015-03-31 |
Meetings
| Meeting | Purpose | When | Vidyo Room | IRC Backchannel |
| Channel Status | Raise quality concerns with the Release Management team | 10:00 Pacific on Tuesday & Thursday | ReleaseCoordination | #planning |
| Firefox QA | Meet the Desktop QA team and hear what they're working on | 8:30am Pacific on Wednesdays | DesktopQA | #qa |
| QA Team | Meet the entire QA team and hear what they're working on! | 1:30am Pacific on Wednesdays | QA | #qa |
Nightly
During the 6 weeks that Firefox 37 is on the Nightly channel, QA will focus on helping with the Firefox iteration planning, as well as with crash reporting and triaging newly reported bugs. The earlier we can get these bug reports into shape for developers to prioritize them and work on them, the more likely they'll be fixed by release in April.
During the 37 Nightly cycle we will be working to help determine the state of the Electrolysis (e10s) project. e10s will be ready to move to Aurora if all bugs marked with tracking-e10s:m6+ and lower are fixed in Nightly.
Reference: https://wiki.mozilla.org/QA/Desktop_Firefox/Walkthroughs/Release_Coordination#Nightly
- Questions for workweek
- Each topcrash should have a developer assigned, a QA contact, and tracking + or -.
- We should decide on a threshold for "crisis" level crash spikes/crash rates. (Different for startup, plugin, crashes or specific platforms)
- What do we want to do with the iteration process. Continue assigning QA contact, verification + or -?
- We should encourage the use of "feature" or verification needed keywords/flags.
- What, if any, conditions would actually block or delay the move to aurora?
- End of cycle status
- Total bugs filed affecting 37:
- Bugs fixed / verified on 37:
- Conditional signoff for merge: (date, who signed off)
- QE signoff:
Aurora
Continue triaging incoming bugs with community help. Test e10s issues.
- File crashes, escalate bad crashes.
- Track feature milestones (for example the e10s tracking flags.)
- Should have testing plans for features that we know may be turned off /on conditionally.
- link to release notes. review & update.
Reference (and migration / signoff plan: https://wiki.mozilla.org/QA/Desktop_Firefox/Walkthroughs/Release_Coordination#Aurora)
Beta
During the Beta cycle, there are at least 9 beta releases. Communication with the release coordination, release engineering, and automation teams is key.
QA analyzes the results of functional, remote, and update tests running on jenkins. We create config files for the update tests, check their validity on mciconf and run them on at least two channels for each beta release cycle. A big part of this work currently is going through the test results to figure out why test failures occurred (infrastructure, tests themselves, actual Firefox bug).
Pivotal bugs may need verification during each beta cycle.
- link to release notes. review & update.
- crash evaluation/escalation.
- feature evaluation.
QA Activities
QA wanted
The following tracks bugs which have requests for urgent QA assistance.
- Choose a bug to test from the list below
- Read it and make sure you understand what information is needed (this may be steps or URLs to reproduce, a regression range, or something else altogether)
- Use the latest build of this Firefox version and test until you've discovered the information necessary. Ask for help if you need it.
- Report this information to the bug and remove the qawanted keyword
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Stability
This section tracks bugs representing the most urgent stability issues. Consult this wiki for more information.
- Ensure new and explosive crashes have actionable bug reports which are in progress
- Top Crashes - ensure the highest ranked crashes have actionable bug reports which are in progress
- Untriaged Bugs - ensure bugs are actionable and in the correct component
26 Total; 26 Open (100%); 0 Resolved (0%); 0 Verified (0%);
- Notes for followup
Unconfirmed Bug Triage
The following tracks triage and testing of incoming, unconfirmed bug reports.
- Choose a bug to test from the list below
- Use the latest Nightly build to confirm the bug reproduces
- Flag with reporter with needinfo if you cannot reproduce and need more information
- Set the status to NEW and ensure the bug is in the appropriate component if you can reproduce the bug (provide as much detail about your testing as possible)
- If it's a Firefox bug you may want to add the firefox-backlog=? flag to it.
All Unconfirmed Bugs
68 Total; 68 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Unchanged Since One Week
These bugs may need extra attention.
66 Total; 66 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Unchanged Since One Month
These are likely to be confusing or non-reproducible issues. We should make decisions to either close these or tag these unactionable, and filter them out
66 Total; 66 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Verification Needed Bugs
- Review the bugs below in the Pending Triage section and select a bug you want to test
- Make sure you understand the bug before you begin testing it
- Test on a previously known broken build to make sure you can reproduce the bug
- Test on the latest build from the branches which are fixed to confirm the bug no longer reproduces
- Mark the bug VERIFIED FIXED if the bug appears to be fixed and set the appropriate status-firefox flag to verified
- Reopen the bug if it still reproduces
Iteration Development
Firefox development during Nightly works on two-week iterations as of 2014. This section tracks the bugs selected for development in these iterations. Please consult the Iteration Dev Walkthrough and the Firefox/IterativeDevelopment page for more information on this process.
- Ensure all bugs are marked qe-verify:+ or -
- Ensure all qe-verify:+ bugs have a QA Contact (The Feature Owner page may help here)
- Ensure all selected bugs are VERIFIED before the end of the iteration
- Anything incomplete at the end of the iteration will be automatically carried over to the next iteration
108 Total; 0 Open (0%); 74 Resolved (68.52%); 34 Verified (31.48%);
Milestones
Aurora Migration
Post-merge Work (as soon as updates are disabled):
- [DONE] MM-CI - configure the mozilla-aurora_update testrun on MM-CI to use the auroratest channel (before first Aurora builds are generated)
Pre-sign-off Checks:
- [DONE] Automation - document all Mozmill test failures (on functional tests) and memory usage regressions (on endurance tests - note that those are only run on nightly, so you look for regressions that happened there). Bugs for those are usually filed by the automation team, but check that they are on top of that.
- [DONE] Features - all scoped features are signed off as ready for Aurora by owners. (If you haven't heard anything to the contrary, that is probably true, but make sure we don't know of blocking issues.)
- [DONE] Bugs - document and review any reported bugs and issues, nominate them for tracking if serious (i.e. make sure all bugs needed to be tracked have at least a request for that up).
- [DONE] Stability - review crash stats before sign-off to raise any red flags.
- [DONE] L10n - contact L10n drivers (usually :Pike) to see if there are any known localization issues.
Post-sign-off Checks (as soon as updates are enabled again):
- [DONE] MM-CI - configure the mozilla-aurora_update testrun on MM-CI to use the aurora channel
- [DONE] Updates - previous versions of Aurora update to the new version (check a few old builds manually once next round of new builds is available)
Betas
Sign-off emails
- For Beta 1 and RC, sign off on beta-cdntest, RelMan needs to give the "go" for pushing out
- For Betas in between, directly send "go" for pushing when beta-cdntest is OK.
Beta 1
Build Information
- build1: 192f6746dc45 (ID: 20150223185154)
Testing
- Manual - Firefox 37 Beta 1
- [DONE] Exploratory testing covering: Youtube, Flash, Bing search with HTTPS, No DevEdition carried from Aurora, In-content Preferences, EME
- [DONE] Bug verification
Bugs Reported
| ID | Summary | Resolution |
|---|---|---|
| 1136648 | A new tab is opened with the results if a search is performed from a pinned about:home tab | WONTFIX |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Beta 2
Build Information
- build1: 67a12d77e65d (ID: 20150302192546)
Testing
- Manual - Firefox 37 Beta 2
- [DONE] Regression testing covering: Printing
- [DONE] Exploratory testing covering: Youtube, Open H264, Loop
- [DONE] Bug verification
Bugs Reported
7 Total; 7 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Beta 3
Build Information
- build1: 00bad6e2ffbc (ID: 20150305191659)
Testing
- Manual - Firefox 37 Beta 3
- [DONE] Regression testing covering: WebGL, Breakpad
- [DONE] Exploratory testing covering: Flash
- [DONE] Verification of new EME UI implementation
- [DONE] Bug verification
Bugs Reported
5 Total; 5 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Beta 4
Build Information
- build1: 89b593b91e5e (ID: 20150309191715)
Testing
- Manual - Firefox 37 Beta 4
- [DONE] Regression testing covering: Video, Audio, Web Compatibility
- [DONE] Exploratory testing covering: Graphics
- [DONE] Bug verification
Bugs Reported
9 Total; 9 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Beta 5
Build Information
- build1: 17af3ddb4a24 (ID: 20150312193711)
Testing
- Manual - Firefox 37 Beta 5
- [DONE] Regression testing covering: Add-ons
- [DONE] Exploratory testing covering: YouTube (default player), WebGL, WebRTC
- [DONE] Bug verification
Bugs Reported
10 Total; 10 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Beta 6
Build Information
- build1: bb7b546e6188 (ID: 20150316202753)
Testing
- Manual - Firefox 37 Beta 6
- [DONE] Regression testing covering: Secure Browsing, PDF
- [DONE] Exploratory testing covering: YouTube (default player), Flash
- [DONE] Bug verification
- [DONE] Smoke testing covering: Hello
Bugs Reported
23 Total; 23 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Beta 7
Build Information
- build1: 9b93e6033d5d (ID: 20150319212106)
Testing
- Manual - Firefox 37 Beta 7
- [DONE] Regression testing covering: Plugins, Update with root owned files, Scrolling & zooming, Session Restore, Mac OSX Signing, Mac OSX 32-bit Mode
- [DONE] Exploratory testing covering: Youtube (default player), Crash Reporter, Add-ons
- [DONE] Bug verification
Bugs Reported
11 Total; 11 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Release Candidate
Build Information
- build1: 7ec23d08cf32 (ID: 20150324194038)
- build2: 29182ac68a26 (ID: 20150326190726)
Testing
- Manual - Firefox 37 RC
- [DONE] Exploratory testing covering: Youtube (default player), Webmail, WebGL, Web compatibility
- [DONE] Bug verification
Build 2 (done because of bug 1147521):
- Manual - Firefox 37 RC build 2
- [DONE] Sanity testing covering: Youtube (default player), Web compatibility
- [DONE] Bug verification for fixes landed in Build 2
- Automated (configs for ondemand)
- This is the 37.0 release build. We should test updates on beta-cdntest for a preliminary sign-off (Release Management must give the "go" for pushing to beta), then on beta after the push to beta, and then on the day before release (Monday), after a full sign-off and push to that channel, run tests on release-cdntest.
- [DONE] Updates on beta-cdntest channel (report)
- [DONE] Updates on beta channel (report)
- [DONE] Updates on release-cdntest channel (report)
- [DONE] Updates on release channel (report)
Bugs Reported
13 Total; 13 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Release 37.0
Build Information
- See Release Candidate Build 2
Testing
- Update Testing - see Release Candidate Build 2
- Throttle Testing (see Walkthrough for details)
- Used commands:
./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/WINNT_x86-msvc/en-US/release/Windows_NT%206.3/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/Darwin%2013.4.0/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/Linux_x86-gcc3/en-US/release/Linux%203.13.0-45-generic%20%28GTK%202.24.23%29/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/Linux_x86_64-gcc3/en-US/release/Linux%203.16.0-30-generic%20%28GTK%202.24.25%29/default/default/update.xml
- Results
- After release push (expected to be @ 25%), 2015-03-31: Win32: 22% - Mac: 21% - Linux32: 24% - Linux64: 24%
- Rest skipped due to 37.0.1 release
- Results
37.0.1
Build Information
- build1: 833c11cfceec (ID: 20150402191859)
Sign-off Criteria
- Mozmill functional automation ran with/without unexpected failures
- Mozmill update automation ran with/without unexpected failures
- No blocking regression, stability, or support issues discovered
Testing
- Manual - Firefox 37.0.1
- [DONE] Exploratory testing covering: Web Compatibility, WebGL
- [DONE] Bug verification of drivers and ride along fix
- Throttle Testing (see Walkthrough for details)
- Used commands:
./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/WINNT_x86-msvc/en-US/release/Windows_NT%206.3/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/Darwin%2013.4.0/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/Linux_x86-gcc3/en-US/release/Linux%203.13.0-45-generic%20%28GTK%202.24.23%29/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/36.0.4/20150320202338/Linux_x86_64-gcc3/en-US/release/Linux%203.16.0-30-generic%20%28GTK%202.24.25%29/default/default/update.xml
- Results
- After release push (expected to be @ 25%), 2015-04-03: Win32: 24% - Mac: 26% - Linux32: 23% - Linux64: 23%
- After disabling updates (expected to be @ 0%), never done.
- After fully enabling updates (expected to be @ 100%), 2015-04-07: Win32: 100% - Mac: 100% - Linux32: 100% - Linux64: 100%
- Results
Bugs Reported
5 Total; 5 Open (100%); 0 Resolved (0%); 0 Verified (0%);
37.0.2
Build Information
- build1: a7ee2c1f2cba (ID: 20150415140819)
Sign-off Criteria
- Mozmill functional automation ran without unexpected failures
- Mozmill update automation ran without unexpected failures
- No blocking regression, stability, or support issues discovered
Testing
- Manual - Firefox 37.0.2
- [AT RISK] Exploratory testing covering: Web Compatibility, WebGL
- [DONE] Bug verification of drivers and ride along fixes
- Throttle Testing (see Walkthrough for details)
- Used commands:
./throttle.sh https://aus3.mozilla.org/update/3/Firefox/37.0.1/20150402191859/WINNT_x86-msvc/en-US/release/Windows_NT%206.3/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/37.0.1/20150402191859/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/Darwin%2013.4.0/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/37.0.1/20150402191859/Linux_x86-gcc3/en-US/release/Linux%203.13.0-45-generic%20%28GTK%202.24.23%29/default/default/update.xml ./throttle.sh https://aus3.mozilla.org/update/3/Firefox/37.0.1/20150402191859/Linux_x86_64-gcc3/en-US/release/Linux%203.16.0-30-generic%20%28GTK%202.24.25%29/default/default/update.xml
- Results
- After release push (expected to be @ 25%), 2015-04-20: Win32: 24% - Mac: 24% - Linux32: 26% - Linux64: 23%
- After fully enabling updates (expected to be @ 100%), 2015-04-23: Win32: 100% - Mac: 100% - Linux32: 100% - Linux64: 100%
- Results
Bugs Reported
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 400 [1] => Bad Request ) ) 1