TESTING

Testing was done after the system was put in place. This was done in two ways namely Unit Testing and integration testing. Test Plan The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan will identify items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing. The purpose of the software test plan is such as:

To achieve the correct code and ensure all Functional and Design

Requirements are implemented as specified in the documentation.

To provide a procedure for Unit and System Testing.

To identify the test methods for Unit and System Testing.

Process of Test Plan

Identify the requirements to be tested. All test cases shall be derived using the current design specification.

Identify particular test to use to test each module.

Identify the expected results for each test.

Perform the test.

Document the test data, test cases used during the testing process.

The following explain the ways in which testing is done.

Unit Testing

Unit testing was carried out on individual modules of the system to ensure that they are fully functional units. We did this by examining each unit, for example the student profile page. It was checked to ensure that it functions as required and that it adds student’s data and other details and also ensured that this data is sent to the database. The success of each individual unit gave us the go ahead to carryout integration testing. All identified errors were dealt with.

 Integration Testing

We carried out integration testing after different modules had been put together to make a complete system. Integration was aimed at ensuring that modules are compatible and they can be integrated to form a complete working system. For example we tested to ensure that when a user is logged in, he/she is linked to the appropriate page, and also could access the database.