QA/Firefox3.5/TestPlan: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3.5
Jump to navigation Jump to search
Line 41: Line 41:
|class="header"|Test Plan Location
|class="header"|Test Plan Location
|class="header"|QA Contact
|class="header"|QA Contact
|class="header"|Dev Contact
|class="header"|Size
|class="header"|Size
|class="header"|FF or Platform?
|class="header"|FF or Platform?
Line 48: Line 49:
|?
|?
|?
|?
|dietrich?
|S
|S
|Ff
|Ff
Line 58: Line 60:
|?
|?
|Tracy
|Tracy
|dietrich
|L
|L
|Ff
|Ff
Line 69: Line 72:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 76: Line 80:
|?
|?
|marcia
|marcia
|
|
|
|Pf
|Pf
Line 83: Line 88:
|?
|?
|?
|?
|jdaggett/zack
|
|
|Pf
|Pf
Line 93: Line 99:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 100: Line 107:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 107: Line 115:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 114: Line 123:
|?
|?
|?
|?
|robarnold, dbaron
|
|
|Pf
|Pf
Line 121: Line 131:
|?
|?
|?
|?
|dbaron
|
|
|Pf
|Pf
Line 128: Line 139:
|?
|?
|Tracy
|Tracy
|
|
|
|Pf
|Pf
Line 135: Line 147:
|
|
|marcia
|marcia
|
|
|
|Pf
|Pf
Line 142: Line 155:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 149: Line 163:
|?
|?
|?
|?
|dholbert
|
|Pf
|
|-
|ACID 3
|?
|?
|Roc or dbaron
|
|
|Pf
|Pf
|
|
|-
|-
|<video> Decoders
|video Decoders
|?
|?
|?
|?
|roc/cdouble?
|
|
|Pf
|Pf
Line 168: Line 192:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 175: Line 200:
|?
|?
|?
|?
|
|
|
|Pf
|Pf
Line 181: Line 207:
|Memory Leaks
|Memory Leaks
|[http://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks Memory Leaks Test Plan]
|[http://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks Memory Leaks Test Plan]
|Tomcat
|Tomcat
|Tomcat
|
|

Revision as of 16:58, 22 July 2008

« Firefox3.1

Top Critical issues for QA

This is a working list that QA is using to request be fixed or completed for the Upcoming Fx3 Milestones.

If you have untracked issues in these areas, please enter them here:

  • Design still incomplete?
  • Major bugs blocking your feature that should be addressed?
  • Major bugs blocking overall regression of the trunk that should be fixed before shipping?

Overview

Firefox 3 QA Test Strategy

The goal of this Overall Test Plan is to lay out our testing strategy, communicate it to others, and track the status.

Major QA Activities:

  • New feature testing - see below
  • L10n testing
  • Milestone testing

Firefox 3.1 Central

Requirements and Scheduling

Test Areas

Feature Focused Areas

Key: L = Large (3-6 weeks) M = Medium (2-4 weeks) S = Small (1-2 weeks)

Test Plan Template

Feature Area and Spec Test Plan Location QA Contact Dev Contact Size FF or Platform? Description
AwesomeBar ? ? dietrich? S Ff
Places ? Tracy dietrich L Ff
Worker Threads ? ? Pf
Offline/Local Storage ? marcia Pf
Downloadable Fonts ? ? jdaggett/zack Pf
Native JSON ? ? Pf
WHATWG <canvas> text API ? ? Pf
AwesomeBar Improvements ? ? Pf
Border Image ? ? robarnold, dbaron Pf
Media Queries ? ? dbaron Pf
Bulk Tagging ? Tracy Pf
Ctrl-Tab marcia Pf Boriss's blog post
Cross Site XHR ? ? Pf spec issues?
SMIL ? ? dholbert Pf
ACID 3 ? ? Roc or dbaron Pf
video Decoders ? ? roc/cdouble? Pf
  • Core element patch has landed
  • --enable-media on trunk?
  • Ogg Vorbis/Theora backend could get review, but legal issues may block
  • Need to push GStreamer and Quicktime backends to patch submission
  • DirectShow backend playing some movies, needs more work
SVG Image Decoding ? ? Pf
Query Selectors ? ? Pf spec issues?
Memory Leaks Memory Leaks Test Plan Tomcat Tomcat Pf Checking for memory leaks and asserts on debug builds

Regression Areas

  • Top Web accessibility Tests
    • Plugins (eg. Flash, java, AJAX)
    • Extensions (eg. Firebug, NoScript, Fotofox)
    • Themes (eg. Vista, Joga, Simpsons)
    • Top Site Tests (eg. Alexa top 50)
    • Financial Sites (eg. banks, online trading)
  • Accessibility Tests
  • User Performance Testing
  • Major / Minor Update Testing
  • L10N Testing (may coincide with Feature area)
  • Distribution Testing (may coincide with Feature area)

Tiger Team Testing

Daily smoketests are ran against nightly trunk builds. Please see marcia for more information.

Link to Schedule and Assignments

Extensions

The following extensions in the list below will be ran through regression tests during selected milestone releases.

See examples here.

Top Crash reports

The main report is the easiest to view.

Banking and Financial Sites

For these types of sites, we’re asking community members and MoCo QA to state which banks and financial institutions they're willing to test. Please add your name to the list.

L10n Testing with Third Parties

For additional string testing, Mozilla will work with the l10n Team for localization and string testing.

Results link to be posted later.

Review Feedback

In this section, we will roll up all common feedback pulled from external sources that appears common and should be tracked by QA. Feedback sources can include:

Additional References

This section is left to add any additional references relevant to the Firefox 3.1 project