|
|
|
|
|
|
|
|
|
MSF for CMMI Process Improvement > Wiki Pages > Activity - Create or Update System or Verification Test
|
Activity - Create or Update System or Verification Test
|
|
|
|
|
|
Activity Information Create or Update System or Verification Test
DescriptionSystem tests are used to verify that the product is implemented as designed and built correctly. The tester creates system tests by analyzing the design documents in the technical data package and determines what kinds of tests are required to ensure that the code implements the design objectives correctly. Attributes| Element Categories | [CMMI Level 3] VER SP 1.3, [CMMI Track 3] Build, [CMMI Cycle 6] As Needed | | When | Design is reviewed and has no remaining problems. | | Entry Criteria | Technical Data Package: The collection of design documents.
Reference Solution: The design documents and diagrams selected to be implemented in the current iteration. | | Exit Criteria | System Test Case: System tests to verify the code for the design are created and checked into source control. | | Is Required | Yes |
StepsIdentify Required System Tests:
Examine the design documents in the technical data package and the reference solution diagrams. Determine which kinds of tests are required to meet the objectives of the design.
The tests should ensure that any product requirement (interface, safety, security, operational, or functional) incorporated in the design is tested adequately.
Tests should include both positive tests to ensure that the product requirement is implemented properly as well as negative tests to try to break the product and demonstrate that some part of the requirement is not met.
Tests should be automated as much as possible. Consider using Visual Studio Team System testing functionality such as Web tests, load tests, and stress tests. Consider using other automated testing tools available and appropriate for the given design. Consider developing test harnesses to test certain aspects of the design. Create System Tests:
Create the tests that have been identified. For automated tests, create the necessary configuration files and data required by the tool to run the test.
For manual tests, create documentation of the procedures for running the tests.
Check all tests into source control.
|
Last modified at 12/19/2007 10:37 AM by Administrator
|
|
|
|
 |
 |
 |
 |
|