Releases/Firefox 50/Test Plan/Beta/9

From New wiki
Jump to navigation Jump to search

«  Firefox 50 Beta 8 | Firefox 50 Beta 9 | Firefox 50 Beta 10 »

Firefox 50.0 Beta 9 Test Plan

QE recommendation regarding the quality of the build

  • Recommendation based on results from manual testing:
Build 1 SHIP-IT, CONDITIONALLY

Manual Testing summary - Platform Coverage and Areas Tested

  • Testing performed around: Bookmarks and Downloads.
  • Test Cases executed and results: report

Build 1

Platform Build architecture Assignee Results: report
Windows XP x86 (NVIDIA GeForce 210) 32-bit Camelia Badau [DONE]
Windows 10 x86 (Intel HD 520) 32-bit Iulia Cristescu [DONE]
Mac OS X 10.11 (NVIDIA GeForce GT 640M) 64-bit Cristian Comorasu [DONE]
Ubuntu 14.04 x64 (Intel HD Graphics 5500) 64-bit Petruta Rasa [DONE]
Tested Area Testing Type [testrail_link Results]
BOOKMARKS Smoke and Exploratory Testing PASS
DOWNLOADS Smoke Testing FAILED

Features

See the [1] gdoc for a general overview


Feature Owner Status Details Test Plan
Windows Child Mode Iulia Cristescu [ON TRACK] Feature set to release with Firefox 50. There are no concerns at this time, regarding this feature's quality. Test Plan
Pointer Lock API Alexandru Simonca [ON TRACK] Feature set to release with Firefox 50. There are no concerns at this time, regarding this feature's quality. Test Plan
WebM EME support for Widevine Ciprian Georgiu [INVESTIGATION NEEDED] Feature set to release with Firefox 50. At this point, our concerns revolve around the still unresolved bugs: 1298027, 1298030, 1301423 and the recent issue we noticed on the shaka player demo, under Ubuntu (the latter being currently investigated by Bryce Van Dyk). Test Plan

Results

New bugs

<bugzilla> {

"id":"1312013,1312024,1312032,1312036,1312020",
"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":"1126854, 910749, 1287823, 1069134, 1308232, 1308237, 1059343, 1126762, 428378, 1311671, 1311630, 1195053, 1069134, 1126854, 428378, 1209518, 1249000, 1177382, 1043280, 755195, 1247925",
"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