Snowglobe Test Plans/Test Pass 1
Revision as of 16:17, 21 May 2009 by Rob Linden (talk | contribs) (New page: {{TOCright}} == Summary == (insert Snowglobe release notes here) Snowglobe Current Cycle == Resources == (insert links to general QA and process) == Current QAR/JIRA == * {{ji...)
Summary
(insert Snowglobe release notes here)
Resources
(insert links to general QA and process)
Current QAR/JIRA
Test Scope and Strategy
We're planning to model testing on our internal cycle.
We'll investigate the feasibility of doing a broad functionality testpass, along with spot checking and day-to-day usage from the community.
Platforms we'd like to test
- Windows
- XP
- Vista
- Windows 7
- Mac
- Intel Mac
- PowerPC Mac
- Linux
- Distros based on volunteer interest
Test Details
Describes the release and deploy related testing that we will be targeting.
Test Pass #1
- Functional areas
- This test cycle will focus on the overall expected functionality of the viewer, from a user's perspective. All major functionality of the viewer is to be tested and validated against expected behaviours.
- Related Test Plans
- Related Docs
- Release Test Plan
Testing Areas | Description | Test Plan | % Complete | Volunteer | Status |
Viewer Smoke Test | This test has been designed to cover a basic spread of functionality prior to releasing a version to the main grid. | Preview Smoke Test | 0% | ||
UI Tests | UI changes and general UI coverage test plan, on Default and Silver skins. Includes toolbars, menus, UI elements. | Viewer UI Test Plan | 0% | ||
Child jiras | Verify each child jira passes its own test plan | see child jira's Test Plan or Description field | |||
New User Test | Test from a brand new user's perspective | New User Test | 0% | ||
Preferences and General UI Elements | Verify each preference in the Preferences floater individually by selecting and hitting OK. (No formal test plan exists for this.) Unexpected Behaviour = UI issues; settings which change on toggle but before OK; obvious deviation from expected behaviour. The preferences field uses every UI element at least once. | 0% | |||
Appearance Editor Test | Exercise the editor as a new user | Exploratory/Scenario | 0% | ||
Build Tools Test | Build Tools Test | 0% | |||
Bug reporter | Verify bug reporting links take you to appropriate landing pages | 0% |