Professional Documents
Culture Documents
Testing
What is the overall goal of testing? What claims can we make when testing "passes" or "fails" ? Can we prove that our code has no bugs?
testing: systematic attempt to reveal the presence of errors (to "falsify" system)
failed test: an error was demonstrated passed test: no error was found, so far
not used to show absence of errors in software does not directly reveal the actual bugs in the code
2
A software module is a self-contained element of a system Modules are individually tested commonly known as unit testing Next major task is to put the modules, i.e., pieces together to construct the complete system
The objective of system integration testing (SIT) is to build a working version of the system
Putting modules together in an incremental manner Ensuring that the additional modules work as expected without disturbing the functionalities of the modules already put together The system is fully integrated togethr All the test cases have been executed All the severe and moderated defects found have been fixed
3
Defects are detected early It is easier to fix defects detected earlier We get earlier feedback on the health and acceptability of the individual modules and on the overall system Scheduling of defect fixes is flexible, and it can overlap with development
4
Steps in Integration-Testing
1. Based on the integration strategy, select a component to be tested. Unit test all the classes in the component. . 2. Put selected component together; do any preliminary fix-up necessary to make the integration test operational (drivers, stubs) 3. Do functional testing: Define test cases that exercise all uses cases with the selected component 4. Do structural testing: Define test cases that exercise the selected component 5. Execute performance tests 6. Keep records of the test cases and testing activities. 7. Repeat steps 1 to 7 until the full system is tested. The primary goal of integration testing is to identify errors in the (current) component configuration.
T sequence1 est
T sequence2 est
T sequence3 est
System Test
Unit Test D Unit Test E Unit Test F
BIG BANG
Intent demonstrate stability by attempting to exercise an entire system with a few test runs Context bring all components together all at once. All interfaces tested in one go. usually ends in big-bang system dies miserably Entry criteria all components have passed unit testing Exit criteria Test suite passes
11
BIG BANG
Consequences Fails then what? Failure diagnosis is very difficult. Even if exit criteria met, many interface faults can still hide.
12
Bottom Up
Entry criteria components pass unit tests Exit criteria interface for each subcomponent has been exercised at least once complete when all root-level components pass test suites
13
Bottom-up Integration
A Layer I C D
Layer II
Layer III
Test A, B, C, D, E, F, G
Test G
Test D,G
Test the top layer or the controlling subsystem first Then combine all the subsystems that are called by the tested subsystems and test the resulting collection of subsystems Do this until all subsystems are incorporated into the test Special program is needed to do the testing, Test stub :
A program or a method that simulates the activity of a missing subsystem by answering to the calling sequence of the calling subsystem and returning back fake data.
Layer III
Test A Layer I
Test A, B, C, D
Test A, B, C, D, E, F, G
Layer I + II
All Layers
Test cases can be defined in terms of the functionality of the system (functional requirements) Writing stubs can be difficult: Stubs must allow all possible conditions to be tested. Possibly a very large number of stubs may be required, especially if the lowest level of the system contains many methods. One solution to avoid too many stubs: Modified top-down
testing strategy
Test each layer of the system decomposition individually before merging the layers Disadvantage of modified top-down testing: Both, stubs and drivers are needed
A target layer in the middle A layer above the target A layer below the target Testing converges at the target layer
How do you select the target layer if there are more than 3 layers?
Layer III
Test F
Test G
Test A, B, C, D, E, F, G
Test A
Top and Bottom Layer Tests can be done in parallel Does not test the individual subsystems thoroughly before integration Solution: Modified sandwich testing strategy
22
23
THANK YOU
25