TestEngineering/UI/AMO/5.0.6 Test Plan: Difference between revisions
< TestEngineering | UI
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
Planned Release date: | Planned Release date: | ||
* Release is currently scheduled for June 2009 | |||
QA Resources: | QA Resources: | ||
* Stephen Donner (irc:stephend) | |||
* Krupa Raj (irc:krupa) | |||
QA Support Level:Level 1. | QA Support Level:Level 1. | ||
| Line 56: | Line 56: | ||
Entry and Exit Criteria: | Entry and Exit Criteria: | ||
* Entry criteria: | |||
**Mocks/Specs are made available to the QA team | |||
**QA team has access to staging server | |||
** 5.0.6 features are ready for testing | |||
* Exit Criteria | |||
**No crashing bugs. | |||
**All features under the scope of this release are functional. | |||
**All P0 and P1 bugs are either fixed or deferred. | |||
**All P0/P1 fixes are verified by QA and marked as such in Bugzilla. | |||
**QA has verified that the fixes have not caused major regression. | |||
Test deliverables: | Test deliverables: | ||
* Test Plan | |||
* Bug reports | |||
* Interim status updates | |||
Assumptions and Risk Management: | Assumptions and Risk Management: | ||
* Assumptions: | |||
** There is no schedule slippage from development. | |||
**No feature creep. | |||
**QA has the latest specs;QA is always informed of any changes to the project | |||
* Risks and their management: | |||
**Need to fill information here | |||
Revision as of 23:15, 11 May 2009
AMO 5.0.6 test plan
MOCK-UPS/Specs:
http://people.mozilla.com/~jscott/bandwagon/clearleft/v11/
STAGING SERVER: 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.
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:
- Mocks/Specs are made available to the QA team
- QA team has access to staging server
- 5.0.6 features are ready for testing
- Exit Criteria
- No crashing bugs.
- All features under the scope of this release are functional.
- All P0 and P1 bugs are either fixed or deferred.
- All P0/P1 fixes are verified by QA and marked as such in Bugzilla.
- 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:
- There is no schedule slippage from development.
- No feature creep.
- QA has the latest specs;QA is always informed of any changes to the project
- Risks and their management:
- Need to fill information here