SAD-Need For Testing

Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. Inadequate testing or non-testing leads to errors. This creates two problems

1. The time lag between the cause and the appearance of the problem and
2. The effect of system errors on files and records within the system

System testing is done to make the user known of the system before implementation.

The first test of a system is to see whether it produces the correct outputs. No other test can be more crucial. A variety of other tests are done

1. Online response – Online systems must have a response time that will not cause a hardship to the user. One way to test this is to input many transactions during peak hours and time the response to each online function to establish a true performance level.

2.Volume - We create as many records as would normally be produced to verify that the hardware and software will function correctly. The user is asked to provide test data for volume testing

3. Stress testing – The purpose of stress testing is to prove that the candidate system does not malfunction under peak loads. Unlike volume testing where time is not a factor, we subject the system to a high volume of data over a short period of time. This simulates an online environment where a high volume of activities occur.

4. Recovery and security- A forced system failure is induced to test a backup recovery procedure for file integrity. Inaccurate data are entered to see how the system responds in terms of error detection and protection. Related to file integrity is a test to demonstrate that data and programs are secure from unauthorized access.

5. Usability documentation and procedure – The usable test verifies the user-friendly nature of the system. This relates to normal operating and error-handling procedures.
SAD-Need For Testing Reviewed by 1000sourcecodes on 19:38 Rating: 5
Powered by Blogger.