Releases/Firefox 51/Test Plan

From MozillaWiki
Jump to: navigation, search

Summary

This page is to track testing of Firefox 51 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 might be changing due to recent reorgs.

The QA efforts are mostly split up between two teams:

  • Engineering QA
    • team reports to Ryan VanderMeulen
    • the Project Manager (and main contact) for the team is Rares Bologa
    • team is based in Romania (most part) and Las Vegas (5 people)
    • the team mainly tests the Desktop app, but covers the Mobile (Android, iOS) side as well
    • main responsibilities:
      • Feature Testing - new Firefox features, prior to landing and during Nightly
      • Bug Triage - older as well as incoming Unconfirmed bugs
      • Bug Investigation - various investigation as requested by other people (e.g. finding steps, setting component, finding regression windows)
      • Misc - other miscellaneous requests
  • Release QA Desktop and Release QA Mobile
    • team reports to Lawrence Mandel
    • the Project Manager (and main contact) for the team is Florin Mezei
    • team is based in Romania
    • main responsibilities:
      • Build Validation - mostly Beta, Release, and ESR builds (including automated ondemand update, and throttling tests)
      • Feature Testing - new features not covered by the Engineering QA team, and those covered by the Engineering QA team after they enter Aurora
      • Bug Verification - verifying the most important / high risk fixes, with focus on those closer to release
      • Bug Investigation - various investigation as requested by other people (e.g. finding steps, setting component, finding regression windows)
      • Misc - other miscellaneous requests

Schedule

Please consult the Rapid Release Calendar for more information.

Milestone Date Checks
Nightly 2016-08-01 Conduct daily stability and bug triage, ensure features are owned
Aurora Migration 2016-09-12 Conduct testing to ensure Firefox 48 Aurora builds are okay, sign off for updates on Friday
Aurora Updates enabled 2016-09-16 Continue daily stability and bug triage, ensure features are tested
Beta Uplift 2016-11-08 Review testing and sign off every beta release
Release 2017-01-24 Review tests and sign off release

Meetings

Meeting Purpose When Vidyo Room IRC Backchannel Notes
Channel Status Raise quality concerns with the Release Management team 10:00 AM Pacific on Tuesday & 08:00 AM Pacific on Thursday ReleaseCoordination #planning Notes archive

Nightly

While Firefox 51 is on the Nightly channel, QA will mainly focus on:

  • Feature Testing - EngQA team (for Firefox features assigned to them) + RelQA team (for other new features - Platform or Firefox)
  • Triaging newly reported bugs - EngQA team
  • Bug Verification - mostly RelQA - with main focus on: fixes related to new features, fixes tracked as Sprint work, fixes for major bugs

Reference: https://wiki.mozilla.org/QA/Desktop_Firefox/Walkthroughs/Release_Coordination#Nightly

End of cycle status
  • Total bugs filed affecting 51: 2294
  • Bugs fixed / verified on 51: 1775 Fixed / 140 Verified
  • Conditional signoff for merge: September 19, 2016, Sylvestre Ledru (email sent to release-drivers at 2:11 PM UTC)
  • QE signoff: N/A

Developer Edition (Aurora)

While Firefox 51 is on the Aurora channel, QA will mainly focus on:

  • Signing off Aurora 51 prior to enabling updates - RelQA
  • Feature Testing - RelQA team
    • Should have testing plans for features that we know may be turned off /on conditionally
    • Full in-depth testing should be completed before merge to Beta
  • Triaging newly reported bugs - EngQA team
  • Bug Verification - mostly RelQA - with main focus on: fixes related to new features, fixes for major bugs

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 several beta releases. Communication with the release coordination, release engineering, and automation teams is key.

While Firefox 51 is on the Beta channel, QA will mainly focus on:

  • Signing off each Beta build prior to being pushed to the beta channel - RelQA
  • Feature Testing - RelQA team
    • Focus is on fixes that land in Beta, and Regression and Smoke testing
  • Triaging newly reported bugs - EngQA team
  • Bug Verification - mostly RelQA - with main focus on: fixes related to new features, fixes for major bugs, fixes assessed as high risk

QA also analyzes the results of OnDemand Update tests running on Jenkins. We create config files for the update tests, check their validity, and run them on at least two channels for each beta release cycle.

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
ID Summary Status Qa contact Component

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
  • topcrash bugs

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.

Queries:

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

Queries:

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, to make sure we don't get any red on aurora update tests)

Pre-sign-off Checks:

  • [DONE] Manual Smoke testing - ensure there are no major issues blocking release to the aurora channel
    • Areas covered: Web Compatibility, Audio Compatibility, Video Compatibility, Plug-in Compatibility, WebGL, Add-on Compatibility, Crash Reporter, and Build Branding
    • Signed off by Andrei Vaida on September 23 - detailed test results
  • [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.)
    • WebGL 2.0 = YELLOW - Owner = Bogdan Maris (ReleaseQA)
    • FLAC Support = GREEN - Owner = Ciprian Georgiu (ReleaseQA)
    • New box-model theme = STAYS IN NIGHTLY - Owner = Cristian Comorasu (ReleaseQA)
    • One-off searches from Awesomebar = STAYS IN NIGHTLY - Owner = Liviu Cirdei (EngineeringQA)
      • Large number of open bugs - Recommendation is to keep the feature in Nightly 52 -> feature is pref'ed on only in Nightly for now
    • New Find Toolbar = STAYS IN NIGHTLY - Owner = Brindusa Tot (EngineeringQA)
      • Large number of open bugs - Recommendation is to keep the feature in Nightly 52 -> feature is pref'ed on only in Nightly for now
    • Indicator for streaming or permissions = YELLOW - Owner = Adrian Florinescu (EngineeringQA)
      • New issues that may impact the feature - Conditionally signed off to enter Aurora, with recommendation to fix the new issues
    • Download Panel "Show All Downloads" dropmarker = YELLOW - Owner = Adrian Florinescu (EngineeringQA)
      • New issues that may impact the feature - Conditionally signed off to enter Aurora, with recommendation to fix the new 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) - NO known blockers reported in Channel Meeting from September 22nd
  • [DONE] Stability - review crash stats before sign-off to raise any red flags - looks good (based on report from September 22nd Channel Meeting)
  • [DONE] L10n - contact L10n drivers (usually :Pike) to see if there are any known localization issues - signed off by Francesco Lodolo on September 22nd
  • [DONE] Send final QE sign-off - Sent by Florin Mezei on September 23rd

Post-sign-off Checks (as soon as updates are enabled again):

Betas

Beta 1

Build Information

Testing

  • Manual - Firefox 51 Beta 1
    • [DONE] Smoke and Exploratory Testing with focus on: WebGL2, FLAC support, Indicator for device permissions, Zoom indicator, and Web Compatibility.
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 2

Build Information

Testing

Beta 3

Build Information

Testing

  • Manual - Firefox 51 Beta 3
    • [DONE] Smoke and Exploratory Testing with focus on: Bookmarks, OS X 32-bit mode, and OS X Signing.
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 4

Build Information

Testing


Beta 5

Build Information

Testing

Beta 6

Build Information

Testing

Beta 7

Build Information

Testing

Beta 8

Build Information

Testing

Beta 9

Build Information

Testing

Beta 10

Build Information

Testing

Beta 11

Build Information

Testing

Beta 12

Build Information

Testing

  • Manual - Firefox 51 Beta 12
    • [DONE] Smoke and Exploratory Testing with focus on: Search, Add-on Compatibility, Printing and Customization.
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)

Beta 13

Build Information

Testing

Beta 14

Build Information

Testing

Release Candidates

51.0 RC

Build Information

Testing

  • Manual - Firefox 51 (RC1)
    • [DONE] Smoke and Exploratory Testing with focus on: Web Compatibility (main focus on Drag & Drop file uploading).
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • [DONE] Updates on beta-cdntest channel (report)
    • [DONE] Updates on beta channel (report)
    • [NOT STARTED] Updates on release-cdntest channel (report) - SKIPPED (RC build 2 was created)
    • [NOT STARTED] Updates on release channel (report) - SKIPPED (RC build 2 was created)

51.0 RC2

Build Information

Testing

51.0.1 Build 2

Build Information

51.0.1 Build 3

Build Information