Releases/Firefox 68/Test Plan

Summary

The purpose of this page is to track the testing of Firefox 68 from Nightly to Release, and post Release if needed.

Release schedule

• Release Scheduling calendar
• Rapid Release calendar

Status meetings

The Channel Status meeting is used to raise quality concerns with the Release Management team.

• When: every Tuesday (10:00 AM Pacific) and Thursday (08:00 AM Pacific)
• Where: ReleaseCoordination (Vidyo Room)
• IRC backchannel: #planning
• Meeting notes: notes archive

QA points of contact

Communication channels

• Slack: #qa-coordination

Firefox for Desktop

Engineering QA

• Reporting to: Tom Grabowski, Tania Maity
• Softvision Manager: Rares Bologa
• Team Leads: Brindusa Tot
• Offices: Romania (EEST), Argentina (GMT-3)
• Responsible for: new feature testing, Nightly build readiness, Nightly build regression testing, bug triage, bug verification, bug investigation

Release QA

• Reporting to: Tom Grabowski, Tania Maity
• Softvision Manager: Andrei Vaida
• Team Leads: Bogdan Maris, Cornel Ionce
• Office: Romania (EEST)
• Responsible for: new feature testing, Beta build readiness, Developer Edition build readiness, ESR build readiness, RC build readiness, Dot release build readiness, Chemspill build readiness, bug verification, bug investigation

Firefox for Mobile

Release QA

• Reporting to: No-Jun Park
• Softvision Manager: Ioana Chiorean
• Team Lead: Sorina Florean
• Office: Romania (EEST)
• Responsible for: todo

Firefox for iOS QA

• Reporting to: No-Jun Park
• Softvision Manager: Ioana Chiorean
• Team Lead: Catalin Suciu
• Office: Romania (EEST)
• Responsible for: todo

AMO, WebExtensions

Add-ons QA

• Reporting to: Krupa Raj
• Softvision Manager: Rares Bologa
• Team Leads: Victor Carciu, Madalin Cotetiu
• Office: Romania (EEST)
• Responsible for: todo

SHIELD, Normandy, Subscription services

Experiments QA

• Reporting to: Krupa Raj
• Softvision Manager: Rares Bologa
• Team Leads: Paul Oiegas
• Office: Romania (EEST), Argentina (GMT-3)
• Responsible for: todo

QA activities

New feature readiness

All new features tested by QA and shipping with Firefox 68 are available here.

The feature testing process followed by QA is available here.

Bug fix verification

• Daily verification of uplifted bugs - these are uplifts, triaged daily and verified under ~48hrs
• Ongoing verification of Nightly bugs - this is the general bug verification done throughout the Nightly cycle; it sometimes overlaps with uplifts verification; also involves active monitoring of qe-verify? bugs
• Ongoing verification of Beta bugs - this is the general bug verification done throughout the Beta cycle; it sometimes overlaps with uplifts verification; also involves active monitoring of qe-verify? bugs
• On-demand verification of bugs - these are special requests (ideally coming in through PI, but also through Bugzilla needinfo, chat or emails)
• Periodical verification of security bugs - these are post-critsmash bugs, triaged and verified ~every 2wks

Unconfirmed bug triage

This is the triage conducted by Engineering QA.

Security bug triage

This is the post-CritSmash triage conducted by Engineering QA (on Nightly) and Release QA (on Beta, Release, ESR).

Bug investigation

This is the daily check and investigation of new regressionwindow-wanted bugs, conducted by Engineering QA and Release QA.

Nightly 68 milestones

[early/mid cycle] Nightly build readiness

Scope: assess build readiness for shipping to Beta by testing Nightly periodically and providing a list of issues (if any) that need to be addressed before the merge (more on this).

Nightly 68.0a1 <date1>

• Build: 68.0a1 (commit, ID) - Sign off_Status
  • [NOT STARTED] Functional testing (manual) → report
    • New bugs – regressions: ID1, ID2, IDN | non-regressions: ID1, ID2, IDN
    • Known bugs – high-impact: ID1, ID2, IDN | medium/low-impact: <bug list>

[prior to merge] Nightly regression testing

Nightly 68.0a1 <date1>

• Build: 68.0a1 (commit, ID) - Sign off_Status
  • [NOT STARTED] Regression testing (manual) → report
    • New bugs – regressions: ID1, ID2, IDN | non-regressions: ID1, ID2, IDN
    • Known bugs – high-impact: ID1, ID2, IDN | medium/low-impact: <bug list>

[optional] [prior to merge] Nightly new feature smoke testing

Note: this is optional, based on available QA bandwidth.

Beta/DevEd 68 milestones

Developer Edition build readiness

Scope: assess build stability periodically (around every 2 weeks) to make sure we are shipping quality products to our Developer Edition users from the aurora update channel (more on this).

DevEd 68.0b1

• Build: 68.0b1-build1 (commit, ID) - Sign off_Status
  • Functional tests (manual):
    • [NOT STARTED] Smoke, Regression and Exploratory testing on _ → report
    • [NOT STARTED] Bug fix verification – <bug list>
  • Update tests (manual):
    • [NOT STARTED] aurora-cdntest → report
    • [NOT STARTED] aurora → report

Beta build readiness

Beta 68.0b3

• Build: 68.0b3-build1 (commit, ID) - Sign off_Status
  • Functional tests (manual):
    • [NOT STARTED] Smoke, Regression and Exploratory testing on _ → report
    • [NOT STARTED] Smoke testing on Ubuntu snap package → report
    • [NOT STARTED] Smoke testing on DLL interceptor → report
    • [NOT STARTED] Bug fix verification – <bug list>
  • Update tests (manual):
    • [NOT STARTED] beta-cdntest, aurora-cdntest → report
    • [NOT STARTED] beta, aurora → report

Release 68 milestones

RC1 68.0

• Build: 68.0-build1 (commit, ID) - Sign off_Status
  • Functional tests (manual):
    • [NOT STARTED] Smoke, Regression and Exploratory testing on _ → report
    • [NOT STARTED] Smoke testing on Ubuntu snap package → report
    • [NOT STARTED] Smoke testing on Windows Acer builds → report
    • [NOT STARTED] Bug fix verification – <bug list>
  • Update tests (manual):
    • [NOT STARTED] beta-cdntest → report
    • [NOT STARTED] beta → report
    • [NOT STARTED] release-localtest → report
    • [NOT STARTED] release-cdntest → report
    • [NOT STARTED] release → report