Releases/Firefox 49/Test Plan

From MozillaWiki
Jump to: navigation, search

Summary

This page is to track testing of Firefox 49 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-04-25 Conduct daily stability and bug triage, ensure features are owned
Aurora Migration 2016-06-06 Conduct testing to ensure Firefox 48 Aurora builds are okay, sign off for updates on Friday
Aurora Updates enabled 2016-06-10 Continue daily stability and bug triage, ensure features are tested
Beta Uplift 2016-08-01 Review testing and sign off every beta release
Release 2016-09-13 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 49 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 49:
  • Bugs fixed / verified on 49:
  • Conditional signoff for merge: (date, who signed off)
  • QE signoff:

Developer Edition (Aurora)

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

  • Signing off Aurora 49 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 49 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

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
  • 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):

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 and the Crash Reporter
    • Signed off by Cornel Ionce on June 9th - 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.)
  • [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.
  • [DONE] Send final QE sign-off - Sent by Florin Mezei on June 10th

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

Betas

Beta 1

Build Information

Testing

  • Manual - Firefox 49 Beta 1
    • [DONE] Smoke Testing with focus on the new features in Firefox Beta 49: Text to Speech on Desktop and Text to Speech in Reader View.
      • Requires access to Test Rail to see results
    • [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)
      • All tests failed due to bug 1291658 - mitigated by rebuilding all jobs and manually setting the TEST_PACKAGES_URL and BUILDID parameters
    • [DONE] Updates on beta channel (report)
      • All tests failed due to bug 1291658 - mitigated by rebuilding all jobs and manually setting the TEST_PACKAGES_URL and BUILDID parameters

Beta 2

Build Information

Testing

Beta 3

Build Information

Testing

Beta 4

Build Information

Testing

  • Manual - Firefox 49 Beta 4
    • [DONE] Smoke & Exploratory Testing with focus on: Migration, Mac OS X Signing, and Mac OS X 32-bit mode.
      • Requires access to Test Rail to see results
    • [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)
    • Failures in Functional Automation for a few locales on OS X 10.10
      • Caused by unexpected resolution setting on the machines - bug 1295626
      • Issue fixed by Henrik Skupin - all tests passed upon re-building

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

  • Manual - Firefox 49 Beta 9
    • [DONE] Smoke Testing with focus on: Session Restore and Sync & FxA.
      • Requires access to Test Rail to see results
    • [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)
    • [NOT STARTED] Updates on beta channel (report)
      • Not run because the build was not released to the "beta" channel - because of bug 1299908

Beta 10

Build Information

Testing

Release Candidates

49.0 RC

Build Information

Testing

  • Manual - Firefox 49.0 RC
    • [DONE] Smoke and Regression Testing with focus on: Sync & Firefox Accounts and Web Compatibility.
      • Requires access to Test Rail to see results
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • This is a candidate for the 49.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)

49.0 RC2

Build Information

Testing

  • Manual - Firefox 49.0 RC2
    • [DONE] Smoke Testing with focus on General Web Compatibility.
      • Requires access to Test Rail to see results
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • This is a candidate for the 49.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)


49.0 RC3

Build Information

Testing

  • Manual - Firefox 49.0 RC3
    • [DONE] Smoke Testing with focus on General Web Compatibility.
      • Requires access to Test Rail to see results
    • [DONE] Bug verification with focus on the latest fixes to land in this build.
  • Automated (configs for ondemand)
    • This is a candidate for the 49.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)


49.0 RC4

Build Information

  • Build 4: 49.0RC4 | [1] | cset: 416dc3163a1f (ID: 20160916101415)

Testing

  • Manual - Spot checks on various platforms by SV in Las Vegas
  • Automated (configs for ondemand)
    • This is a candidate for the 49.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)

Release 49.0

Build Information

  • See Release Candidate Build 4

Testing

49.0.1 Build 3

Build Information

49.0.2 Build 1

Build Information

49.0.2 Build 2

Build Information

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_49/Test_Plan&oldid=1152040"