Releases/Firefox 58/Test Plan

From MozillaWiki
< Releases
Revision as of 13:27, 10 November 2017 by Cornel.ionce (talk | contribs) (Developer Edition)

Jump to: navigation, search

Summary

This page is to track testing of Firefox 57 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 Lawrence Mandel
    • 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 Beta
      • 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

Milestone Date Checks
Nightly 2017-11-14 Conduct daily bug triage, regular build validation, and feature testing
Beta 2017-01-08 Feature testing and sign off every beta release, regular testing of DevEdition builds
Release 2018-01-16 Review tests and sign off release

Please consult the Rapid Release Calendar for more information.

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 58 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)
  • Regular Nightly validation - 3 rounds per cycle - EngQA team + RelQA team, alternately
  • Triaging newly reported bugs - EngQA team
  • Bug Verification - both teams - 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 57: [TBD]
  • Bugs fixed / verified on 57: [TBD] / [TBD]
  • Conditional signoff for merge: <date>, <person> (email sent to release-drivers at
  • QE signoff: N/A

Beta

During the Beta cycle, there are several beta releases. Communication with the release coordination, release engineering, and automation teams is key.

While Firefox 58 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
  • Regular validation of DevEdition builds - about once every two weeks
  • 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

Regular Nightly Validation

SIGN-OFF DATE SIGN-OFF STATUS REASON(S) MAJOR ISSUES MINOR ISSUES TEST REPORT
2017-09-23 PENDING
  • TBD
2017-12-13 PENDING - - - -
2018-01-04 PENDING - - - -

Nightly Migration

Pre-sign-off Checks:

  • [NOT STARTED] Manual Smoke testing - ensure there are no major issues blocking release to the beta channel
    • Areas covered: TBD
    • Signed off by <name> on <date>
  • [NOT STARTED] Features - all scoped features are signed off as ready for Beta 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.)

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

  • None yet for migration of Nightly to Beta

Developer Edition

Note: Developer Edition builds are usually signed off once every two weeks.
BUILD SIGN OFF ENCOUNTERED BUGS
Status Reason(s) Test Report New Known (old)
58.0b1-build1 SHIP IT
  • No new issues uncovered.
  • Known issues are low-impact.
link
  • Regressions: none.
  • Non-regressions: none.
  • High-impact: none.
  • Low-impact: link.
58.0b2-build1 TBD
  • No new issues uncovered.
  • Known issues are low-impact.
link
  • Regressions: none.
  • Non-regressions: none.
  • High-impact: none.
  • Low-impact: link.

Beta

Note: Beta builds are usually signed off twice a week.