System Testing and Maintenance
UNIT TESTING
The procedure level testing is made first. By giving improper inputs, the errors occurred are noted and eliminated. Then the web form level testing is made. For example storage of data to the table in the correct manner.
In the company as well as seeker registration form, the zero length username and password are given and checked. Also the duplicate username is given and checked. In the job and question entry, the button will send data to the server only if the client side validations are made.
The dates are entered in wrong manner and checked. Wrong email-id and web site URL (Universal Resource Locator) is given and checked.
INTEGRATION TESTING
Testing is done for each module. After testing all the modules, the modules are integrated and testing of the final system is done with the test data, specially designed to show that the system will operate successfully in all its aspects conditions. Thus the system testing is a confirmation that all is correct and an opportunity to show the user that the system works.
VALIDATION TESTING
The final step involves Validation testing, which determines whether the software function as the user expected. The end-user rather than the system developer conduct this test most software developers as a process called “Alpha and Beta Testing” to uncover that only the end user seems able to find.
The compilation of the entire project is based on the full satisfaction of the end users. In the project, validation testing is made in various forms. In registration form Email id for the user is verified.
The compilation of the entire project is based on the full satisfaction of the end users. In the project, validation testing is made in various forms. In registration form Email id for the user is verified.
VERIFICATION TESTING
Verification is a fundamental concept in software design. This is the bridge between customer requirements and an implementation that satisfies those requirements.
This is verifiable if it can be demonstrated that the testing will result in an implementation that satisfies the customer requirements. Inadequate testing or non-testing leads to errors that may appear few months later. This will create two problems Time delay between the cause and appearance of the problem.
The effect of the system errors on files and records within the system.
This is verifiable if it can be demonstrated that the testing will result in an implementation that satisfies the customer requirements. Inadequate testing or non-testing leads to errors that may appear few months later. This will create two problems Time delay between the cause and appearance of the problem.
The effect of the system errors on files and records within the system.
MAINTENANCE
The objectives of this maintenance work are to make sure that the system gets into work all time without any bug. Provision must be for environmental changes which may affect the computer or software system. This is called the maintenance of the system. Nowadays there is the rapid change in the software world. Due to this rapid change, the system should be capable of adapting these changes. In our project the process can be added without affecting other parts of the system.
Maintenance plays a vital role. The system liable to accept any modification after its implementation. This system has been designed to favor all new changes. Doing this will not affect the system’s performance or its accuracy.
