Releases/Firefox 46/Test Plan/Beta/2
Jump to navigation
Jump to search
« Firefox 46 Beta 1 | Firefox 46 Beta 2 | Firefox 46 Beta 3 »
Firefox 46.0 Beta 2 Test Plan
- Release Week: Mar 14th, 2016. Plan is to ship this build on Friday, Mar 18th 2016 (Release Calendar)
- QA Contacts: Robert Kaiser; Florin Mezei; Andrei Vaida
- IRC: irc://irc.mozilla.org#qa ping kairo; FlorinMezei; avaida
- Build 2: 46.0b2-build2 | 2a62a6f3237e | (ID: 20160314144540)
- Build 3: 46.0b2-build3 | 5904e3eb711d | (ID: 20160316065941)
QE recommendation regarding the quality of the build
- Recommendation based on results from manual testing:
| Build 2 | NOT TESTED |
|---|
| Build 3 | GOOD FOR RELEASE |
|---|
Manual Testing summary - Platform Coverage and Areas Tested
- Testing performed around: Search, Search suggestions and the Awesomebar.
- Test Cases executed and results: report
Build 3
| Platform | Build architecture | Assignee | Results: report |
| Windows XP x86 (AMD Radeon R7360) | 32-bit | Iulia Cristescu | [DONE] |
| Windows 8.1 x64 (AMD Radeon HD 3000) | 64-bit | Andrei Vaida | [DONE] |
| Mac OS X 10.11 (Intel Iris Pro) | 64-bit | Camelia Badau | [DONE] |
| Ubuntu 14.04 x86 (Intel HD 2500) | 32-bit | Petruta Rasa | [DONE] |
| Tested Area | Testing Type | Results |
| Search | Regression Testing | PASS |
| Awesomebar & search suggestions | Regression Testing | PASS |
Features
See the Feature Release Tracking gdoc for a general overview
| Feature | Owner | Status | Details | Test Plan |
|---|---|---|---|---|
| APZ | Petruta Rasa | [ON TRACK] | Feature targeted for Firefox 46 - final QA sign-off at the end of Beta 46 | Test Plan |
Results
New bugs
<bugzilla> {
"id":"", "include_fields":"id,summary,status,resolution"
} </bugzilla>
Known Issues - also seen in previous builds
Major issues also seen in previous builds
<bugzilla> {
"id":"", "include_fields":"id,summary,status,resolution"
} </bugzilla>
Low impact issues also seen in previous builds
<bugzilla> {
"id":"1240729, 1222107, 1192169, 1224552, 1240727, 1227734, 1239663, 1122470", "include_fields":"id,summary,status,resolution"
} </bugzilla>
Branch Bug Fix Verifications
<bugzilla> { "id":"", "include_fields":"id,summary,status,resolution" } </bugzilla>
Status tags
- [NOT STARTED] - {{mnotstarted}} - little or no work has started on this task
- [ON TRACK] - {{mok}} - task is actively being worked on and those assigned feel comfortable and confident in the quality of the build.
- [DONE] - {{mdone}} - task is completed and those assigned feel comfortable and confident in the quality of the build.
- [AT RISK] - {{mrisk}}- blocking bug / high number of bugs / other confidence-shakers makes us feel not comfortable with the quality of the build.
- [IN PROGRESS] - {{mprog}} - actively being tested on
- [INVESTIGATION NEEDED] - {{minvest}} - more investigation needed