Activity Information Test Planning
DescriptionAnalyze the requirements and change requests along with the existing architecture, domain model, and user interface flow model; then determine a list of test tasks for the quality assurance team to perform in order to validate the specification for the iteration. Attributes| Element Categories | [CMMI Track 3] Build, [CMMI Level 2] PP SP 1.1, [CMMI Report 12] Scenario Details | | Entry Criteria | User Acceptance Tests:
The validation tests written against the requirements.
Scenarios:
The list of scenarios accepted for the iteration.
QoS Requirements:
The list of quality of service requirements accepted for the iteration.
Functional Requirements:
The list of functional requirements accepted for the iteration.
Operational Requirements:
The list of operational requirements accepted for the iteration.
Security requirements:
The list of security requirements accepted for the iteration.
Change Requests:
The list of change requests accepted for the iteration.
User Interface Flow Model:
The user interface flow or interaction wire frame model for the product or iteration.
Domain Model:
An object or data domain model describing the product domain.
Existing Architecture:
Any documentation describing the existing logical architecture and physical data center or deployment environment. | | Exit Criteria | Test Tasks:
Task work items of type Test describing all the testing activities required for the iteration. | | Is Required | Yes |
StepsAnalyze User Acceptance Tests:
For each scenario, quality of service requirement, functional requirement, operational requirement, security requirement, and change request, identify the user acceptance tests. Consider the environment required for the test including test data, test setup and runs, and test result reporting. Plan tasks for the creation of test data, the setup of the test environment, and the performance and reporting of tests. Plan Exploratory Testing:
Set time aside in the estimate for exploratory testing by explicitly creating tasks for exploratory testing. This will ensure that exploratory testing is a scheduled part of the testing activity.
|
Last modified at 12/19/2007 10:37 AM by Administrator
|
|