ANOOP GANGWAR 5 TH SEM SOFTWARE TESTING MASTER OF COMPUTER APPLICATION-V Sem

System/Software Testing Error detection and removal determine level of reliability well-planned procedure - Test Cases done by independent quality assurance group(except for unit testing)

3 Stages of Testing Module or unit testing. Integration testing, Function testing. Performance testing. Acceptance testing. Installation testing.

4 Unit Testing Program reviews. Formal verification. Testing the program itself. –black box and white box testing.

Sometime called structural testing or glass-box testing Derivation of test cases according to program structure Knowledge of the program is used to identify additional test cases Objective is to exercise all program statements (not all path combinations) White-box testing

White box testing - binary search example int search ( int key, int [] elemArray) { int bottom = 0; int top = elemArray.length - 1; int mid; int result = -1; while ( bottom <= top ) { mid = (top + bottom) / 2; if (elemArray [mid] == key) { result = mid; return result; } // if part else { if (elemArray [mid] < key) bottom = mid + 1; else top = mid - 1; } } //while loop return result; } // search

Binary search equivalence partitions

Binary search - test cases

Path testing The objective of path testing is to ensure that the set of test cases is such that each path through the program is executed at least once The starting point for path testing is a program flow graph that shows nodes representing program decisions and arcs representing the flow of control Statements with conditions are therefore nodes in the flow graph

Describes the program control flow. Each branch is shown as a separate path and loops are shown by arrows looping back to the loop condition node Used as a basis for computing the cyclomatic complexity Cyclomatic complexity = Number of edges - Number of nodes +2 Program flow graphs

The number of tests to test all control statements equals the cyclomatic complexity Cyclomatic complexity equals number of conditions in a program Useful if used with care. Does not imply adequacy of testing Although all paths are executed, all combinations of paths are not executed Cyclomatic complexity

Binary search flow graph

Black-box testing An approach to testing where the program is considered as a ‘black-box’ The program test cases are based on the system specification Test planning can begin early in the software process

Black-box testing

Integration testing Tests complete systems or subsystems composed of integrated components Integration testing should be black-box testing with tests derived from the specification Main difficulty is localising errors Incremental integration testing reduces this problem

Incremental integration testing

Stub Testing (Stubs and Drivers) - Unit and Integration testing A Top-Down Integration Testing bcd Stubs Stubs: dummy modules used for testing if higher level modules are working properly. A BCD Stubs efg A BCD EFG

A BCD EFG Bottom-Up Integration testing a BCD EFG Driver: dummy modules used for issuing calls to lower modules and testing if the lower modules are working properly. Driver b EF c G a D

20 Regression Testing Check for defects propagated to other modules by changes made to existing program –Representative sample of existing test cases is used to exercise all software functions. –Additional test cases focusing software functions likely to be affected by the change. –Tests cases that focus on the changed software components.

21 Thread Testing Testing set of actions associated with particular module functions.

22 Smoke Testing Software components already translated into code are integrated into a build. A series of tests designed to expose errors that will keep the build from performing its functions are created. The build is integrated with the other builds and the entire product is smoke tested daily using either top-down or bottom integration.

23 System Testing Recovery testing –checks system’s ability to recover from failures Security testing –verifies that system protection mechanism prevents improper penetration or data alteration Stress testing –program is checked to see how well it deals with abnormal resource demands Performance testing –tests the run-time performance of software

24 Performance Testing Stress test. Volume test. Configuration test (hardware & software). Compatibility. Regression tests. Security tests. Timing tests. Environmental tests. Quality tests. Recovery tests. Maintenance tests. Documentation tests. Human factors tests.

25