Monday, January 4, 2010

6.9 System Testing:

System testing is actually a series of different tests whose primary purpose is to fully exercise the computer based system. Although each test has different purpose, all work should be verified that all subsystem elements have properly integrated and performed allocation function.

6.9.1 Recovery testing
Recovery testing is a system test that enforces the software it fail ion a variety of ways and verifies that recovery is properly performed. If the recovery is automatic , reinitialisation,check pointing mechanism and data recovery are evaluated for correctness. If the recovery requires human intervention ,the mean=time is calculated to determine whether it is acceptable limits.

6.9.2 Security testing
Security testing attepts to verify that protection mechanism built into system will in fact protect it from unauthorized person’s access to system.

6.9.3 Stress testing
Stress tests are designed to handle programs with abnormal situations. Stress testing executes a system in a manner that demands resources in abnormal quantity, frequency of volume. For example these are some of the test cases designed in stress testing.
Special tests may be designed that generate ten interrupt per second, when one or two is the average rate.
a. input data rates may be increased by an order for magnitude to determine how input function will respond.
b. Test cases that require maximum memory or other resources may be executed.
c. Test cases that may cost thrashing in virtual operating system may be designed.
d. Test cases may cause excessive hunting for the disk resident data may be created.

6.9.4 Performance testing
Integrated testing performance testing occurs throughout all steps in this testing process. Even at the unit level, performance of an individual module may be assessed as white box texts are conducted. However it is not until all system elements are fault integrated that the true performance of the system can be ascertained. Performance test is often coupled with the stress testing and often require both hardware and software instrumentation. External instrumentation can monitor execution intervals, log events as they occur and sample machine states on regular basis.By experimenting a system, the tester can uncover the situation that lead to degradation and possible system failure.

Read More......

6.8 User Level Testing:

 User threads testing
The testing includes the simultaneous access of all the modules of the system by different users. This helps in testing of the software in the multi-user environment.
 Stress testing
To test the software of the maximum stress it has to under go during the execution process. And how much load it can withstand.
 Human factor testing
This testing helps in measuring the human error factor which can affect the quality of the project hence can be reduced by taking various precautions.

Read More......

6.7 Configuration Testing:

Configuration testing is a process to test whether software is compatible with multiple system configurations i.e software functions properly with other elements of the system.

Read More......

6.6 Validation Testing:

At the culmination of integrated testing, software is assembled as package and final series of software test i.e. Validation Testing begins. Validation Testing begins. Validation succeeds when a software function in a manner that can be reasonably expected by the customer. In this step we can perform alpha and beta testing. The customer conducts alpha testing at developer’s site. Beta testing is conducted site customer site by end user of the software.

Read More......

6.5 Integration Testing:

Once the entire module have undergone unit testing they are integrated and again tested for bugs using a technique called integration testing.
There are two methods: incremental and non incremental integration. In non incremental integration the tendency is to construct the program using “Big Bang Approach”.
Two different incremental strategies are: Top down and Bottom up integration.
6.5.1 Top down Integration:
Top down testing is incremental approach. Modules /components are integrated by moving downwards through control hierarchy, beginning with main control module.

6.5.2 Bottom up Integration
Bottom up testing begins construction and testing with automatic modules. Because modules are integrated from the bottom up processing required for modules subroutines to a given level is always available and the need for stubs is eliminated.
The steps of bottom up integration strategy:
• Low level modules are combined into clusters that perform a specific software sub function.
• A driver is written to co-ordinate test case input and output.
• The cluster is tested.

Read More......
 
Template design by Amanda @ Blogger Buster