Confirmed users
1,904
edits
Releases/Firefox 63/Test Plan: Difference between revisions
Jump to navigation
Jump to search
m
→Beta
Bogdan.maris (talk | contribs) m (→Nightly) |
Bogdan.maris (talk | contribs) m (→Beta) |
||
| Line 68: | Line 68: | ||
During the Beta cycle, there are several beta releases. Communication with the release coordination, release engineering, and automation teams is key. | During the Beta cycle, there are several beta releases. Communication with the release coordination, release engineering, and automation teams is key. | ||
While Firefox | While Firefox 63 is on the Beta channel, QA will mainly focus on: | ||
* Signing off each Beta build prior to being pushed to the beta channel - RelQA | * Signing off each Beta build prior to being pushed to the beta channel - RelQA | ||
* [https://docs.google.com/ | * [https://docs.google.com/spreadsheets/d/1IdIMWOrYymTVKgCPiPoxWQ3xlYBNbGX_UC2rAX1YRYY/edit Feature Testing] - RelQA team | ||
** Focus is on fixes that land in Beta, and Regression and Smoke testing | ** Focus is on fixes that land in Beta, and Regression and Smoke testing | ||
* Regular validation of DevEdition builds - about once every two weeks | * Regular validation of DevEdition builds - about once every two weeks | ||
| Line 76: | Line 76: | ||
* Bug Verification - mostly RelQA - with main focus on: fixes related to new features, fixes for major bugs, fixes assessed as high risk | * 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 | QA also analyzes the results of update testing which is done manually at this stage. We run them on at least two channels for each beta release cycle. | ||
Pivotal bugs may need verification during each beta cycle. | Pivotal bugs may need verification during each beta cycle. | ||