Confirmed users
1,477
edits
TestEngineering/UI/AMO/5.0.6 Test Plan: Difference between revisions
TestEngineering/UI/AMO/5.0.6 Test Plan (view source)
Revision as of 23:05, 11 May 2009
, 11 May 2009no edit summary
(Blanked the page) |
No edit summary |
||
| Line 1: | Line 1: | ||
[https://intranet.mozilla.org/Community_Take_Action_Week_2009 CTAW project page] | |||
'''AMO 5.0.6 test plan''' | |||
'''MOCK-UPS/Specs:''' | |||
http://people.mozilla.com/~jscott/bandwagon/clearleft/v11/ | |||
'''STAGING SERVER:''' | |||
[https://preview.addons.mozilla.org/en-US/firefox/ preview.addons.mozilla.org] | |||
Acceptance doc: | |||
? | |||
Planned Release date: | |||
* Release is currently scheduled for June 2009 | |||
QA Resources: | |||
* Stephen Donner (irc:stephend) | |||
* Krupa Raj (irc:krupa) | |||
QA Support Level:Level 1. | |||
[https://wiki.mozilla.org/QA/Execution/Web_Testing/Support_Levels See all our Support levels] | |||
QA will cover: | |||
* Detailed Browser Compatibility testing | |||
* Doctype validation | |||
* Basic Formatting and Appearance | |||
* Link validation | |||
* User interactions | |||
o Need to specify details here | |||
* JavaScript-disabled testing for: (1/4 day) | |||
o Front page | |||
o Browsing by category | |||
Other: | |||
* Accessibility testing-Marco? | |||
* Localization testing-???[May have to involve the Localization community early on] | |||
What is out of scope: | |||
* Unit Testing | |||
* Performance testing (Load, Volume, Stress) | |||
* White Box testing | |||
* Security testing | |||
Team needs to help cover: | |||
* Verifying copy is correct | |||
* Ensuring that final designs are correct | |||
Entry and Exit Criteria: | |||
* Entry criteria: | |||
o Mocks/Specs are made available to the QA team | |||
o QA team has access to staging server | |||
o CTAW website is ready for testing | |||
* Exit Criteria | |||
o No crashing bugs. | |||
o All features under the scope of this release are functional. | |||
o All P0 and P1 bugs are either fixed or deferred. | |||
o All P0/P1 fixes are verified by QA and marked as such in Bugzilla. | |||
o QA has verified that the fixes have not caused major regression. | |||
Test deliverables: | |||
* Test Plan | |||
* Bug reports | |||
* Interim status updates | |||
Assumptions and Risk Management: | |||
* Assumptions: | |||
o There is no schedule slippage from development. | |||
o No feature creep. | |||
o QA has the latest specs;QA is always informed of any changes to the project | |||
* Risks and their management: | |||
o Need to fill information here | |||