|
![](images/b_topleft.gif) |
![](images/b_top.gif) |
![](images/b_topright.gif) |
![](images/b_left.gif) |
Activity:
Perform a Unit Test
![](images/clear.gif) |
![](images/clear.gif) |
Participating Roles
Responsible:
Developer |
A unit test covers a particular area of code, and a combination of unit tests can help developers and testers identify the quality of a particular section of written code. Complete unit tests when the code base changes. A completed unit test gives a definitive answer as to whether the code covered by the unit test is working as expected.
Entry Criteria
Dependencies:
- The unit test is written and verified to represent the item under test.
Sub-Activities
![](images/clear.gif) |
1 |
Identify Appropriate Unit Test |
- Find the most relevant unit test(s) that correspond to the element under test.
|
2 |
Perform a Unit Test |
- Run the unit test on the area under test.
|
3 |
Analyze Test Results |
- As each step is completed, mark each one appropriately using either Pass, Fail, Skip, Warning, or Blocked and add comments when needed.
- If the test fails because the test was written incorrectly, fix the unit test and run the test on the element under test.
- If the test fails because the code under test was written incorrectly, fix the code and rerun the test. Do not open a new bug.
|
4 |
Debug Code |
- Correct problems introduced when writing code for the task.
|
Exit Criteria
![](images/check.gif) |
The unit test achieves code coverage test target or the reason why it does not is documented in the check-in notes. |
![](images/check.gif) |
All unit tests pass. | |
![](images/b_right.gif) |
![](images/b_bottomleft.gif) |
![](images/b_bottom.gif) |
![](images/b_bottomright.gif) |
© 2006 Microsoft Corporation. All rights reserved.
Version 4.1.0 |
![](Source/clear.gif) |