Development Process for Web-Enabled Applications – Unit Testing

Unit Testing

Objective

Unit Testing focuses verification effort on the smallest unit of software design - the program. The unit test is normally white-box oriented, and the step can be conducted in parallel for multiple programs.

Entry Criteria

· Low Level Design document available

· Unit Test Plan available

· Reviewed Source Code available

Process Description

· Identify the test cases based on the low-level Design document (LLD) and Unit Test Plan. Prepare the Test Cases for each program. Refer to the form for Test Plan

TST - F001

· Prepare Test Data for the Test Cases using test plan document. Refer to the form for Test Cases Form - TST – F002.Test data can come from the following sources:

· Existing database

· Simulation of database

· The Test Cases are reviewed using the Document Review Form REV-F001 by either a peer or the project manager. Review comments are to be tracked to closure before testing commences.

· Each unit is tested individually by the team members, through all possible paths, for all possible errors and violations of standards to ensure that it functions properly as a unit and the results of the tests are noted on the Test Results document (refer to TST – F004 Test Results Form).

· Prepare the Unit Test Report based on the unit testing done for each module. It provides summary statistics on the testing conducted, in terms of number of passed and failed test cases and also reports any deviations from the expected result.

Deliverables from the process

· Reviewed Test Cases

· Unit Test Plan along with recorded passed/failed criterion

· Unit Test Report

· Unit Tested Code

Exit Criteria

· Test Report available with all test cases passed successfully

· Traceability matrix updated (Refer to 12.3.5 for format of this matrix)

System Testing

Back to the LinksMultiple eBay Auction | eBay Shopping home page