System Testing
Testing Methodologies and policies
Testing is an activity to verify that a correct system is being built and is performed with
the intent of finding faults in the system. However not restricted to being performed after the
development phase is complete. But this is to carry out in parallel with all stages of system
development, starting with requirement specification. Testing results once, gathered and
evaluated, provide a qualitative indication of software quality and reliability and serve as a basis
for design modification if required a project be set to be incomplete without proper testing.
System testing is a process of checking whether the development system is working
according to the original objectives and requirements. The system should be tested
experimentally with test data so as to ensure that the system works according to the required
specification. When the system is found working, test it with actual data and check performance.
All tests should be traceable to customer requirements. The focus of testing will shift
progressively from programs. Exhaustive testing is not possible. To be more effective, testing
should be one, which has probability of finding errors.
The Following are the attributes of good test
A good test has a high probability of finding an error
A good test is not redundant.
A good test should be “Best of Breed”.
A good test should neither too simple nor too complex.
Levels of Testing
The details of the software functionality tests are given below
The testing procedures that has been used is as follows
Unit Testing Validation Testing
Output Testing Performance Testing
Unit Testing
The first level of testing is called as unit testing. Here the different modules are tested and
the specifications produced during design for the modules. Unit testing is essential for
verification of the goal and to the test the internal logic of the modules. Unit test was conducted
to the different modules of the project. Errors were noted down and corrected down immediately
and the program clarity was increased the testing was carried out during the programming stage
itself. In this step each module is found to be working satisfactory as regard to the expected
output from the module. The modules like Customer Module, Employee Module, Stock Module
etc., were tested.
Validation Testing
The next level of testing is validation testing. Here the entire software is tested the
reference document for this process is the requirement and the goal is to see if the software meets
its requirements.
The requirement document reflects and determines whether the software function as the
user expected. At the culmination of the integration testing, software is completely assembled as
a package, interfacing and corrected and final serious of software test and validation test begins.
The proposed system under construction has been tested by using validation testing and found to
be working satisfactory. After finishing the integration testing, the modules were tested for
validation.
Output Testing
The output of the software should be acceptable to the system user. The output
requirement is defined during the system analysis. Testing of the software system is done against
the output requirements and the output testing was completed with success.
Performance Testing
This project is a system based project, and the modules are interdependent with the other
modules, so the testing cannot be done module by module. So the unit testing is not possible in
the case of this driver. So this system is checked only with their performance to check their
quality.
In case of the unit testing the initialization module is first tested. Since read module and the write
module is interdependent the performance testing is done.
