Unit testing

A series of stand-alone tests are conducted during Unit Testing. Each test examines an individual component that is new or has been modified. A unit test is also called a module test because it tests the individual units of code that comprise the application.

Each test validates a single module that, based on the technical design documents, was built to perform a certain task with the expectation that it will behave in a specific way or produce specific results. Unit tests focus on functionality and reliability, and the entry and exit criteria can be the same for each module or specific to a particular module. Unit testing is done in a test environment prior to system integration. If a defect is discovered during a unit test, the severity of the defect will dictate whether or not it will be fixed before the module is approved.

Sample Entry and Exit Criteria for Unit Testing

Entry Criteria

• Business Requirements are at least 80% complete and have been approved to-date
• Technical Design has been finalized and approved
• Development environment has been established and is stable
• Code development for the module is complete

Exit Criteria

• Code has version control in place
• No known major or critical defects prevents any modules from moving to System Testing
• A testing transition meeting has be held and the developers signed off
• Project Manager approval has been received