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

Project Portal
| See Also Write or Update a Unit Test Walkthrough: Creating and Running Unit Tests |
| ### Next Steps Prepare for Bug Code Review |
| Perform Unit Test for Bug Fix ( 3 : VER : 3 : 3.1 ) Developer
Activity: Perform Unit Test for Bug Fix
Developer
|  |  |  | Build |  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Developer
### Overview A unit test covers a particular area of code, and a combination of unit tests can help developers and testers determine 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 The unit test is written and validated to represent the code under test. The unit test is written and validated to represent the code under test. Updated source code to test is available. Updated source code to test is available. # Sub-Activities
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 as 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
| The unit test achieves code coverage test target or the reason why it does not is documented in the appropriate work item (task or bug).
| All unit tests pass.
| Updated source code that passes all unit tests.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |