User:Mwobensmith/ESR process

ESR process

1. One week prior:

• Clone and update ESR test plan with skeleton details
  • copy/paste template from here if necessary
• Check pushlog for outstanding/important bug fix verifications
• Update test plan with these bugs
  • for normal ESR release, link to VERIFYME query
  • call out any important bugs, especially if it's a chemspill
• Start verifying and/or assigning these bugs with "qawanted"

2. When a build is ready:

• Update test plan.
  • update version number
  • update FTP, HTTP links
  • update build IDs for all platforms
  • update changeset, pushlog
• Set up test Manual Smoketest run in MozTrap
  • Log into moztrap via Persona
  • Visit MozTrap runs
  • Type "esr" in search field
  • Select "esr" result in "name"
  • Find the testrun "Firefox 17.0esr Smoketests" (start date 2012-11-16)
  • Click the clone button for this testrun (looks like two overlapping rectangles)
  • Select pencil icon
  • Change name to "Firefox 17.0.xesr Smoketests"
  • Update dates (usually build day to release day)
  • Save Run
  • Look for your run at top of list with grey icon
  • Click grey icon and select Activate
  • Click the Details button on far left, looks like triangle in a square
  • Right click "run" green button
  • Copy link
  • Paste link in test plan
• Contact Softvision to run manual smoke tests
  • send link to test plan
  • send details on any new platforms and/or priorities
  • Softvision will record the results; review them for any obvious failures

3. At least one day after build, and before ESR release:

• Verify MozMill automated test run
• check MozMill CI dashboard the day after build is generated
  • should be triggered automatically
  • if no results, trigger via ondemand-functional cfg file - will take a few hours
    • LINK TO PASTEBIN EXAMPLE OF CFG FILE
    • EXPLICIT INSTRUCTIONS FOR JENKINS, including links to both instances
  • record test results
  • filter by version, all platforms, date
    • dates are based on GMT timestamp - select a 24-hour window from when the test was started
• update link to report
• record any test failures
• update link to known bugs

4. When updates are ready on esrtest and/or releasetest, perform update testing:

• You will need to connect to BOTH Mozilla-MV and Mozilla-MPT VPN networks
• To run Windows/Linux update tests, go here.
• Take the contents of this page and copy/paste into a text file locally, save as "something.cfg".
• Use it to create a test run
  • Click +admin tab
  • Find item in list "trigger-ondemand"
  • Click on green arrow at the END of this table
  • Upload your file.
  • Go back to main page to view status of tests, and/or wait for mozmill-ci emails.
• To run Mac tests, go here (or: this)
• Again, copy/paste the example CFG file contents from another page
  • Save locally in a text file, name it something.cfg
  • Follow the same instructions as above
• REPEAT THIS FOR EACH CHANNEL TO TEST (esrtest, releasetest, esr)

5. Build signoff

• Send signoff email to release-drivers when:
  • All automated tests pass with no blocking regressions
  • All manual tests pass with no blocking regressions
  • All esrtest/releasetest update testing passes with no regressions
  • All bugs verified
• When esr release channel is ready, repeat "Update testing" above for that channel
  • Send another signoff email when this is complete