Releases/Firefox 28/Test Plan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 76: Line 76:
  | Input type=color
  | Input type=color
  | Manuela Muntean, Paul Silaghi
  | Manuela Muntean, Paul Silaghi
  |  
  | [https://wiki.mozilla.org/QA/Desktop_Firefox/input-type-color Wiki page]
  | [https://bugzilla.mozilla.org/show_bug.cgi?id=930277 1 bug]
  | [https://bugzilla.mozilla.org/show_bug.cgi?id=930277 1 bug]
  |  
  |  

Revision as of 16:12, 4 December 2013

« Firefox 27 | Firefox 28 | Firefox 29 »

Firefox 28 Test Plan

QA Lead: Anthony Hughes

Schedule

  • 2013.10.28: Nightly
  • 2013.12.09: Aurora
  • 2014.01.17: Pre-Beta feature sign-offs
  • 2014.01.21: Beta 1
  • 2014.01.28: Beta 2
  • 2014.01.31: Beta 3
  • 2014.02.04: Beta 4
  • 2014.02.07: Beta 5
  • 2014.02.11: Beta 6
  • 2014.02.14: Beta 7
  • 2014.02.18: Beta 8
  • 2014.02.21: Beta 9
  • 2014.02.25: Beta 10
  • 2014.03.02: Release Candidate
  • 2014.03.03: Final

Nightly

Features

Feature Tracking

Tentative

Sign-off Criteria
  • All user stories covered by manual or automated tests
  • Manual testing complete with no blocking regressions
  • Automated testing complete with no blocking regressions
  • 0 untriaged unconfirmed bugs
  • 0 untriaged unverified fixes
Status
Feature Owner Documentation Tracked Bugs Aurora Merge Sign-off Pre-beta Sign-off
Australis Paul Silaghi, Cornel Ionce Wiki page
Shumway Paul Silaghi, Bogdan Maris Wiki page
Thumbnail Service Alexandra Lucinet Wiki page fixed bugs
Input type=color Manuela Muntean, Paul Silaghi Wiki page 1 bug
Session Restore Cornel Ionce fixed bugs
Disallow enumeration of navigator.plugins Catalin Varga 1 bug
MP4 Support Alexandra Lucient 1 bug
Enable WEBGL_draw_buffers No need for QA owner 1 bug NA NA
Port DOM Promises to Workers No need for QA owner - covered automatically 1 bug NA NA

Fixed Bugs

How to Help
  • Download and install the latest Firefox Nightly
  • Load this list of bug reports
  • Read each bug report until you find one you understand and want to test
  • Download and install the version of Firefox used to report the bug
  • Using the older build, test the claim made in the bug report to see if you can reproduce it
    • If you cannot reproduce the bug move on to another bug or ask the reporter to verify the fix
  • Using the latest Nightly, test to see if you can reproduce the bug
    • If you cannot reproduce the bug set the STATUS to VERIFIED FIXED and add a comment describing your testing
    • If you can still reproduce the bug set the STATUS to REOPENED and add a comment describing your testing
  • Add any bug reopened to the list below using the bug number template (verified fixes will be tracked elsewhere)
  • If you need help, send email to Anthony Hughes with the bug summary in the Subject field
Reopened Bugs

Reported Bugs

Triage unconfirmed bugs.

How to Help
  • Download and install the latest Firefox Nightly
  • Load this list of bug reports
  • Read each bug report until you find one you understand and want to test
  • Test the claim made in the bug report and see if you can reproduce it
  • If you can reproduce the bug, set the STATUS to NEW, add a comment describing your testing, and try to find a regression window
  • Any confirmed bugs should be added to the list below using the bug number template
  • If you need help, send email to Anthony Hughes with the bug summary in the Subject field
Confirmed Bugs

Stability

How to Help
  • Review the Firefox 28 Explosiveness Report
    • Any signatures rising significantly (>= 2.0 explosiveness rating) without a bug number should be reported to Bugzilla and nominated for tracking
    • If there is already a bug report, update the report with the latest numbers
    • Ensure the bug report has the topcrash-platform keyword added (where platform is the platform where crashes occur -- ie. topcrash-win for Windows)
    • Ensure the bug is listed below using the bug number template
  • Review the Firefox 28 Topcrash Report
    • Any signature in the top 10 without a bug number should be reported to Bugzilla and nominated for tracking
    • If there is already a bug report, update the report with the latest ranking information
    • Ensure the bug report has the topcrash-platform keyword added (where platform is the platform where crashes occur -- ie. topcrash-win for Windows)
    • Ensure the bug is listed below using the bug number template
  • Review the Firefox 28 tracked bugs that aren't tracked in 27 or 26.
    • Each bug listed needs to have its rank updated once per week
    • Use the topcrash reports from crash-stats to get the rank for each branch
    • Add this information to the bug report
    • Ensure the bug report has the topcrash-platform keyword added (where platform is the platform where crashes occur -- ie. topcrash-win for Windows)
    • Conversely, remove the topcrash keyword if the crash is no longer in the top-10
  • For each of these tasks, ensure the etherpad is updated with your name and the date checked
Topcrash Bugs
  • bug 934533 Nightly Nov-04, crash in gfxContext::gfxContext(mozilla::gfx::DrawTarget*) if gfx.content.azure.enabled = false
  • bug 931794 startup crash in mozilla::dom::WindowBinding::get_content
  • bug 931911 crash in mozilla::a11y::SelectionManager::ProcessSelectionChanged(nsISelection*)
  • bug 812683 [Win7] startup crash in _d2d_clear_surface @ CContext::RestorePipelineStateImpl w/ASUS GamerOSD
  • bug 937220 mozalloc_abort(char const* const) | NS_DebugBreak | js::AtomizeChars(js::ExclusiveContext*, wchar_t const*, unsigned __int64, js::InternBehavior)
  • bug 805406 crash in gfxContext::PushClipsToDT with Direct2D 1.1 (d3d11.dll 6.2 or 6.3)
  • bug 941869 `anonymous namespace::ReportErrorRunnable::ReportError(JSContext*, mozilla::dom::workers::WorkerPrivate*, bool, mozilla::dom::workers::WorkerPrivate*, nsString const&, nsString const&, nsString const&, unsigned int, unsigned int, unsigned int, unsign...

QA Wanted

How to Help
  • Download and install the latest Firefox Nightly
  • Review this list of bug reports to find a bug you both understand and want to test (each should contain a comment detailing what's needed from QA)
    • If the bug needs steps to reproduce, try to find a reproducible set of steps
    • If the bug needs a regression window, try to find a regression window
    • If the bug is fixed and needs verification, test to confirm you can reproduce the bug on an older build but not the latest build
  • Any tested bugs should be added to the list below using the bug number template
  • Remove the qawanted keyword from any fulfilled request
  • If you need help, send email to Anthony Hughes with the bug summary in the Subject field
Tested Bugs

Testdays

Aurora

Branch Migration

Pre Sign-off Tasks

  • {{|}} Firefox branch migrated (Release Management)
  • {{|}} Mozmill Tests branch migrated (Automation Development)
  • {{|}} Updates throttled on aurora channel (Release Engineering)
  • {{|}} Updates verified throttled on aurora channel (QA)

Sign-off Tasks

  • {{|}} Mozmill Daily functional testruns pass with no failures (report)
  • {{|}} Mozmill Daily auroratest update testruns pass with no failures (report)
  • {{|}} Scope features tested and signed off for Aurora uplift
    • feature...

Post Sign-off Tasks

  • Aurora sign-off email sent (QA)
  • Updates unthrottled on aurora channel (Release Engineering)
  • Updates verified unthrottled on aurora channel (QA)

Beta

Bugs by Status

Retrieved from "https://wiki.allizom.org/index.php?title=Releases/Firefox_28/Test_Plan&oldid=780438"