QA/Firefox 4/Test Plan/WebsocketsTestplan

From MozillaWiki
< QA‎ | Firefox 4‎ | Test Plan
Jump to: navigation, search

Feature (example: add-ons preference UI)

  • Development Status: - In progress (date)
  • Feature Testing: - In progress (date)
  • Team: Olli Pettay (smaug), Matt Evans (mevans)
  • Tracking Bugs:bug 472529 - (websocket) Support for Web sockets' HTML5 Draft Recommendation

Feature Description

Brief description of the feature listed here.

Feature Release Readiness Assessment

The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone. Each milestone link references a section below that discusses the criteria and evaluation that went into the QA go/no-go decision.

Milestone Assessment
#Beta1 N/A
#Beta2 N/A
#Beta3 N/A


Feature Documentation

Item Description Status
#Project_Wiki Wiki Links to all feature related entries
#Developer_Links (blogs) Developer links to feature related sites
#Other_Docs Web links to feature related sites
#Developer_QA_Review Details from developer and qa discussions regarding feature test strategies and issues.


Feature Bug Management

Item Description Status
#Bug_Tracking Top level bugs tracking feature
#Bug_Verification Feature bugs that need verification
#Bug_Triage Links triage bug tasks


Feature Test Items

The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what should be covered. If it is not covered, list it as not covered.

Note: not all items listed below will apply for a given feature

Test Item Description Covered By Status
Item 1 Item 1 Description Developer Tests
Item 2 Item 2 Description Beta tester exposure
#Localization Feature localization
#Accessibility Feature accessibility
#Plugins Plugins compatibility
#Addons Addons compatibility
#Topsites Top internet sites compatibilities


Feature Tests

Automated Tests

Item Description Status
#Developer_Tests Links to automated developer tests
#Mozmill_Tests Links to automated mozmill feature test cases

Manual Tests

Item Description Status
#Smoke_Tests link to smoke tests
#Regression_Tests link to BFT and/or regression tests
#Functional_Tests link to FFT and/or complete functional tests


Community Test Events

Item Description Status
#Testdays Links to test day event results for feature
#Bugdays Links to bug day event results for feature
#Meetups Links to Meetup events for feature


Feature Documentation Details

Project Wiki

  • Provide link to all project related wikis
Link Description Beta feature table


Developer Links


Other Docs


Developer QA Review

The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:

  • Do we have automated tests for the feature?

smaug: Yes. content/base/test should have some tests.

  • What do they cover?

smaug: Look for the tests. (geo: tests look for websocket and _ws_)

  • What do they not cover?

smaug: Evil protocol frames, I think. Basically something that the implementation may not expect to get from server.

  • How well do they cover the feature?

smaug: Hard to say

  • What are the important areas we should focus on?

smaug: Testing websockets in different kinds of environments. Proxies, ssl, etc.

  • What are the dependencies?

smaug: I don't understand this. (geo: discussed briefly on IRC, doesn't seem like there are notable dependencies.)

  • What is our comfort level with this feature in its current state?

smaug: after bug 572975 and bug 573227 things should look pretty good.

  • What feedback would you like from QA?

smaug: Basic testing. Especially when websocket is used with proxies or inside firewalls or something like that.


Feature Release Readiness Assessment Details




Feature Bug Management Details

Bug Tracking

  • Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
Query Name Description
Bug bug 570789 - Add WebSocket support to mochitest blocking bug for websockets
Bug bug 562681 - Update the WebSockets implementation to support the latest version of the protocol


Bug Verification

  • Feature bugs that need verification


Bug Triage

  • Bug triage information


Feature Test Items Details


  • Details of feature localization test requirements



  • Details of feature accessibility test requirements



  • Details of plugins compatibility test requirements



  • Details of addons compatibility



  • Details of top internet sites test requirements


Feature Tests Details

Automated Tests Details

Developer Tests

  • Links to automated developer tests


Mozmill Tests

If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "[mozmill-test-needed]" whiteboard entry to the feature implementation or regression bug.

List of Mozmill Tests:

  • Links to automated mozmill feature test cases


Manual Tests Details


  • links to litmus smoke tests or description



  • links to litmus BFT and/or regression tests description



  • links to litmus FFT and/or complete functional tests description


Community Test Events Details


  • Links to test day event results for feature


  • Links to bug day event results for feature


  • Links to Meetup events for feature