Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| Test a Customer Requirement ( 3 : VAL : 1 : 1.3 ) ( 3 : VAL : 2 : 2.1 ) ( 3 : VAL : 2 : 2.2 ) ( 3 : RD : 1 : 1.1 ) ( 2 : CM : 2 : 2.1 ) Tester
|  | Participating Roles Responsible: Tester Accountable: Tester Consult: Business Analyst Solution Architect Subject Matter Expert Developer Informed: Test Manager Developer Project Manager
### Overview The assignment of a test task to a tester indicates that a customer requirement is ready to be tested. The purpose of testing a customer requirement is to validate that the product implements the requirement as expected by the user. Testing a customer requirement demands performance, security, stress, and load tests to run with no blocking problems. Based on the test results, bug work items are created to document the issues discovered. # Entry Criteria Test Cases The test cases are written and stored with the requirements and scenarios. Quality of Service Requirements The quality of service requirements are validated and have test cases written. Scenarios The scenarios are validated and have test cases written. Threat Model The threat model identifies expected avenues of attack. Task A test task is assigned to the tester. Test Approach Identifies test data and conditions for tests. Personas Personas are used to guide the exploratory testing. When: A test task is assigned to the tester for the current iteration. # Activities
1 | Develop Customer Requirement Tests | Determine type of test. Write performance tests. Write stress tests. Write load tests. Write security tests. Write validation tests.
2 | Select and Run Customer Requirement Tests | Determine tests to run. Set up test environment. Get the build. Run the tests. Analyze test results. Close the test task.
3 | Conduct Exploratory Testing | Optional Limit session length. Meet persona expectations. Envision new goals.
4 | Open a Bug for Customer Requirement | Determine if bug is a duplicate. Open a new bug. Assign the bug.
# Exit Criteria
| Test approach is updated with any new data or considerations.
| A new bug work item is created describing the bug and is assigned to the appropriate developer.
| New scenarios are added to the scenario list.
| New requirements are added to the quality of service requirements list.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |