Skip to main content
Sign In |
  Help (new window)

MSF for Agile Software Development

Go Search
Home
  
MSF for Agile Software Development > Wiki Pages > WorkDefinition - Test a Scenario  

WorkDefinition - Test a Scenario

View All Site Content

Recent Changes
WorkDefinition Information

Test a Scenario

Description

A scenario is divided into test tasks as well as development tasks. These tasks are assigned to testers to develop and run test cases. The assignment of a scenario to test indicates that the functionality has been integrated into a build and is ready to be tested. Validating that a build reflects the functionality envisioned in the scenario requires an understanding of the scenario and its boundary conditions. Validation tests must be written to cover the complete functionality and the boundary conditions of the scenario. Validation tests are run until none are blocked. Bugs are created to report any bugs that were found.

Conduct Exploratory TestingWrite Validation TestsOpen a BugSelect and Run a Test CaseDefine Test Approach

Attributes

Entry Criteria (Dependency)

The scenario has been written, reviewed, and if necessary, storyboarded.

Entry Criteria

A test task for the scenario has been assigned outlining the area of the scenario being tested.

Exit Criteria

All of the validation tests have been run and any resulting bugs have been reported.

Inputs and Outputs

WorkProductInputOutputAllowable States
BugNew
Manual Test(none)
Persona(none)
Quality of Service RequirementResolved
ScenarioActive, Resolved
Scenario Description(none)
TaskActive
Test Approach(none)
Test Result(none)
Web Test(none)

Predecessors

TypeNameDependency Type
Build a ProductFinish-Start
Divide Scenarios into TasksFinish-Start

Successors

TypeNameDependency Type
Fix a BugStart-Start
Release a ProductFinish-Start

Last modified at 12/10/2007 3:34 PM  by Administrator