TOPIC-9: TESTING (Elearning Project)

9. Testing

TestPlan:-This document describes the plan for testing E-Learning Software. All the major testing strategies are specified here; additional testing may be scheduled later, if necessary.

1.Test Units
In this project we will perform two levels of testing: Unit testing & System testing. Because the System is moderate in Size, it is felt that there is no need for elaborate integration testing. The basic units to be tested are:
# Modules to Tables
# Tables to Reports
# Other Units
In addition, some other units may be chosen for testing. The testing for these different units will be done independently.

2.Features To Be Tested
All the functional features specified in the requirement document will be tested. No testing will be done for the performance, as the response time requirement is quite weak.

3.Approach To Testing
For Unit Testing, Structural Testing based on the branch coverage criterion will be used. The goal is to achieve branch coverage of more than 95%. System testing will be largely functional in nature. The focus is on Invalid and Valid cases, Boundary Value and Special Cases.

4.Test Deliverables
The following documents are required (besides this Test Plan):
• Unit test report of each Unit.
• Test case Specification for System Testing
• Test Report for System Testing
• Error Report

The test case specification for System Testing has to be submitted for review before System Testing Commences.

The entire testing- Unit & System will be finished within the month of December. Test case Specifications for the System Testing will be produced while Unit Testing is going on. This Schedule is consistent with the over all schedule of the project. The schedule for the testing is shown in the Project Planning section.

Test Case Specification for System Testing

Here we specify all the test cases that are used for System Testing. First, the different conditions that need to be tested, along with the test cases for testing those condition and the expected output are given. Then the data files used for testing are given. The Test cases are specified with respect to these data files. The Test cases have been selected using functional approach. The goal is to test the different functional requirements, as specified in the requirement document. Test cases have been selected for both Valid as well as Invalid Input.