UNIT TESTING INTEGRATION TESTING AND SYSTEM TESTING Testing
![UNIT TESTING, INTEGRATION TESTING AND SYSTEM TESTING Testing and System Implementation UNIT TESTING, INTEGRATION TESTING AND SYSTEM TESTING Testing and System Implementation](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-1.jpg)
![SOFTWARE ENGINEERING ROADMAP SOFTWARE ENGINEERING ROADMAP](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-2.jpg)
![TESTING: THE BIG PICTURE 3. System tests 2. Integration tests 1. Unit tests Module TESTING: THE BIG PICTURE 3. System tests 2. Integration tests 1. Unit tests Module](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-3.jpg)
![WHAT IS UNIT TESTING? §In computer programming, unit testing is a method by which WHAT IS UNIT TESTING? §In computer programming, unit testing is a method by which](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-4.jpg)
![ROADMAP FOR UNIT TESTING ROADMAP FOR UNIT TESTING](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-5.jpg)
![PLAN FOR UNIT TESTING 1. Decide on the philosophy for unit testing individual engineer PLAN FOR UNIT TESTING 1. Decide on the philosophy for unit testing individual engineer](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-6.jpg)
![Perform Method Testing 1/2 1. Verify operation at normal parameter values (a black box Perform Method Testing 1/2 1. Verify operation at normal parameter values (a black box](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-7.jpg)
![Perform Method Testing 2/2 9. Check normal termination of all loops (part of a Perform Method Testing 2/2 9. Check normal termination of all loops (part of a](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-8.jpg)
![RELATING TESTS TO REQUIREMENTS & DESIGN (1) D-Requirements 3. 2. EC. 1. 2 Qualities RELATING TESTS TO REQUIREMENTS & DESIGN (1) D-Requirements 3. 2. EC. 1. 2 Qualities](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-9.jpg)
![(1) D-Requirements 3. 2. EC. 1. 2 Qualities of Encounter characters Every game character (1) D-Requirements 3. 2. EC. 1. 2 Qualities of Encounter characters Every game character](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-10.jpg)
![Applied to. . . Unit test Concentration Stamina Results in a zero value? 1. Applied to. . . Unit test Concentration Stamina Results in a zero value? 1.](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-11.jpg)
![Applied to. . . Unit test Concentration Stamina Results in a zero value? 2. Applied to. . . Unit test Concentration Stamina Results in a zero value? 2.](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-12.jpg)
![WHY DO WE DO INTEGRATION TESTING? §Unit tests only test the unit in isolation WHY DO WE DO INTEGRATION TESTING? §Unit tests only test the unit in isolation](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-13.jpg)
![INTEGRATION TESTING STRATEGY The entire system is viewed as a collection of subsystems (sets INTEGRATION TESTING STRATEGY The entire system is viewed as a collection of subsystems (sets](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-14.jpg)
![STUBS AND DRIVERS Driver: A component, that calls the Tested. Unit Controls the test STUBS AND DRIVERS Driver: A component, that calls the Tested. Unit Controls the test](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-15.jpg)
![EXAMPLE : THREE LAYER CALL HIERARCHY A C B E Layer I F D EXAMPLE : THREE LAYER CALL HIERARCHY A C B E Layer I F D](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-16.jpg)
![INTEGRATION TESTING: BIGBANG APPROACH INTEGRATION TESTING: BIGBANG APPROACH](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-17.jpg)
![BOTTOM-UP INTEGRATION BOTTOM-UP INTEGRATION](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-18.jpg)
![PROS AND CONS OF BOTTOM UP INTEGRATION TESTING Bad for functionally decomposed systems: Tests PROS AND CONS OF BOTTOM UP INTEGRATION TESTING Bad for functionally decomposed systems: Tests](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-19.jpg)
![TOP-DOWN INTEGRATION TESTING TOP-DOWN INTEGRATION TESTING](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-20.jpg)
![PROS AND CONS OF TOP-DOWN INTEGRATION TESTING q. Test cases can be defined in PROS AND CONS OF TOP-DOWN INTEGRATION TESTING q. Test cases can be defined in](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-21.jpg)
![SANDWICH TESTING STRATEGY Combines top-down strategy with bottom-up strategy The system is view as SANDWICH TESTING STRATEGY Combines top-down strategy with bottom-up strategy The system is view as](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-22.jpg)
![SANDWICH TESTING STRATEGY SANDWICH TESTING STRATEGY](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-23.jpg)
![PROS AND CONS OF SANDWICH TESTING v. Top and Bottom Layer Tests can be PROS AND CONS OF SANDWICH TESTING v. Top and Bottom Layer Tests can be](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-24.jpg)
![MODIFIED SANDWICH TESTING STRATEGY Test in parallel: Middle layer with drivers and stubs Top MODIFIED SANDWICH TESTING STRATEGY Test in parallel: Middle layer with drivers and stubs Top](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-25.jpg)
![MODIFIED SANDWICH TESTING STRATEGY MODIFIED SANDWICH TESTING STRATEGY](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-26.jpg)
![STEPS IN INTEGRATIONTESTING 1. Based on the integration strategy, select a component to be STEPS IN INTEGRATIONTESTING 1. Based on the integration strategy, select a component to be](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-27.jpg)
![WHICH INTEGRATION STRATEGY SHOULD YOU USE? w. . . Top-level components are usually important WHICH INTEGRATION STRATEGY SHOULD YOU USE? w. . . Top-level components are usually important](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-28.jpg)
![SYSTEM TESTING §Functional Testing §Structure Testing §Performance Testing §Acceptance Testing §Installation Testing Impact of SYSTEM TESTING §Functional Testing §Structure Testing §Performance Testing §Acceptance Testing §Installation Testing Impact of](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-29.jpg)
![STRUCTURE TESTING Essentially the same as white box testing. Goal: Cover all paths in STRUCTURE TESTING Essentially the same as white box testing. Goal: Cover all paths in](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-30.jpg)
![FUNCTIONAL TESTING Essentially the same as black box testing ¨ ¨ Goal: Test functionality FUNCTIONAL TESTING Essentially the same as black box testing ¨ ¨ Goal: Test functionality](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-31.jpg)
![PERFORMANCE TESTING ¨ Stress Testing w Stress limits of system (maximum # of users, PERFORMANCE TESTING ¨ Stress Testing w Stress limits of system (maximum # of users,](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-32.jpg)
![TEST CASES FOR PERFORMANCE TESTING ¨ ¨ ¨ Push the (integrated) system to its TEST CASES FOR PERFORMANCE TESTING ¨ ¨ ¨ Push the (integrated) system to its](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-33.jpg)
![ACCEPTANCE TESTING ¨ ¨ Goal: Demonstrate system is ready for operational use ¨ Alpha ACCEPTANCE TESTING ¨ ¨ Goal: Demonstrate system is ready for operational use ¨ Alpha](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-34.jpg)
![TESTING LIFE CYCLE TESTING LIFE CYCLE](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-35.jpg)
![TEST TEAM TEST TEAM](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-36.jpg)
- Slides: 36
![UNIT TESTING INTEGRATION TESTING AND SYSTEM TESTING Testing and System Implementation UNIT TESTING, INTEGRATION TESTING AND SYSTEM TESTING Testing and System Implementation](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-1.jpg)
UNIT TESTING, INTEGRATION TESTING AND SYSTEM TESTING Testing and System Implementation
![SOFTWARE ENGINEERING ROADMAP SOFTWARE ENGINEERING ROADMAP](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-2.jpg)
SOFTWARE ENGINEERING ROADMAP
![TESTING THE BIG PICTURE 3 System tests 2 Integration tests 1 Unit tests Module TESTING: THE BIG PICTURE 3. System tests 2. Integration tests 1. Unit tests Module](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-3.jpg)
TESTING: THE BIG PICTURE 3. System tests 2. Integration tests 1. Unit tests Module combination Module Function
![WHAT IS UNIT TESTING In computer programming unit testing is a method by which WHAT IS UNIT TESTING? §In computer programming, unit testing is a method by which](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-4.jpg)
WHAT IS UNIT TESTING? §In computer programming, unit testing is a method by which individual units of source code are tested to determine if they are fit for use. §A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure. In objectoriented programming a unit is usually a method. Unit tests are created by programmers or occasionally by white box testers. 4
![ROADMAP FOR UNIT TESTING ROADMAP FOR UNIT TESTING](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-5.jpg)
ROADMAP FOR UNIT TESTING
![PLAN FOR UNIT TESTING 1 Decide on the philosophy for unit testing individual engineer PLAN FOR UNIT TESTING 1. Decide on the philosophy for unit testing individual engineer](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-6.jpg)
PLAN FOR UNIT TESTING 1. Decide on the philosophy for unit testing individual engineer responsible (common)? reviewed by others? designed & performed by others? 2. Decide what / where / how to document individual’s personal document set (common)? how / when to incorporate into other types of testing? incorporate in formal documents? use tools / test utilities? 3. Determine extent of unit testing (i. e. , in advance). do not just “test until time expires” prioritize, so that important tests definitely performed 4. Decide how and where to get the test input 5. Estimate the resources required use historical data if available 6. Arrange to track time, defect count, type & source
![Perform Method Testing 12 1 Verify operation at normal parameter values a black box Perform Method Testing 1/2 1. Verify operation at normal parameter values (a black box](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-7.jpg)
Perform Method Testing 1/2 1. Verify operation at normal parameter values (a black box test based on the unit’s requirements) 2. Verify operation at limit parameter values (black box) 3. Verify operation outside parameter values (black box) 4. Ensure that all instructions execute (statement coverage) 5. Check all paths, including both sides of all branches (decision coverage) 6. Check the use of all called objects 7. Verify the handling of all data structures 8. Verify the handling of all files
![Perform Method Testing 22 9 Check normal termination of all loops part of a Perform Method Testing 2/2 9. Check normal termination of all loops (part of a](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-8.jpg)
Perform Method Testing 2/2 9. Check normal termination of all loops (part of a correctness proof) 10. Check abnormal termination of all loops 11. Check normal termination of all recursions 12. Check abnormal termination of all recursions 13. Verify the handling of all error conditions 14. Check timing and synchronization 15. Verify all hardware dependencies
![RELATING TESTS TO REQUIREMENTS DESIGN 1 DRequirements 3 2 EC 1 2 Qualities RELATING TESTS TO REQUIREMENTS & DESIGN (1) D-Requirements 3. 2. EC. 1. 2 Qualities](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-9.jpg)
RELATING TESTS TO REQUIREMENTS & DESIGN (1) D-Requirements 3. 2. EC. 1. 2 Qualities of Encounter characters Every game character has the same set of qualities. Each quality shall be a nonnegative floating point number with at least one decimal of precision. . (2) Design Game. Character Requirements An abstract class with attribute name. . . .
![1 DRequirements 3 2 EC 1 2 Qualities of Encounter characters Every game character (1) D-Requirements 3. 2. EC. 1. 2 Qualities of Encounter characters Every game character](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-10.jpg)
(1) D-Requirements 3. 2. EC. 1. 2 Qualities of Encounter characters Every game character has the same set of qualities. Each quality shall be a nonnegative floating point number with at least one decimal of precision. . Test this method. . . against this requirement RELATING TESTS TO REQUIREMENTS & DESIGN (2) Design Game. Character Requirements An abstract class with attribute name. . . Test this class. . . against this requirement Characters Game. Character Encounter Characters Encounter. Character adjust. Quality()
![Applied to Unit test Concentration Stamina Results in a zero value 1 Applied to. . . Unit test Concentration Stamina Results in a zero value? 1.](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-11.jpg)
Applied to. . . Unit test Concentration Stamina Results in a zero value? 1. Within range No: Test 1. 1. 1 etc. Partitioning of Range for Unit Testing 1 of 2 Yes: Test 1. 2. 1 etc.
![Applied to Unit test Concentration Stamina Results in a zero value 2 Applied to. . . Unit test Concentration Stamina Results in a zero value? 2.](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-12.jpg)
Applied to. . . Unit test Concentration Stamina Results in a zero value? 2. Outside range No: Test 2. 1. 1 etc. Partitioning of Range for Unit Testing 2 of 2 Yes: Test 2. 2. 1 etc.
![WHY DO WE DO INTEGRATION TESTING Unit tests only test the unit in isolation WHY DO WE DO INTEGRATION TESTING? §Unit tests only test the unit in isolation](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-13.jpg)
WHY DO WE DO INTEGRATION TESTING? §Unit tests only test the unit in isolation §Many failures result from faults in the interaction of subsystems §Often many Off-the-shelf components are used that cannot be unit tested §Without integration testing the system test will be very time consuming §Failures that are not discovered in integration testing will be discovered after the system is deployed and can be very expensive.
![INTEGRATION TESTING STRATEGY The entire system is viewed as a collection of subsystems sets INTEGRATION TESTING STRATEGY The entire system is viewed as a collection of subsystems (sets](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-14.jpg)
INTEGRATION TESTING STRATEGY The entire system is viewed as a collection of subsystems (sets of classes) determined during the system and object design. The order in which the subsystems are selected for testing and integration determines the testing strategy Big bang integration (Nonincremental) Bottom up integration Top down integration Sandwich testing Variations of the above
![STUBS AND DRIVERS Driver A component that calls the Tested Unit Controls the test STUBS AND DRIVERS Driver: A component, that calls the Tested. Unit Controls the test](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-15.jpg)
STUBS AND DRIVERS Driver: A component, that calls the Tested. Unit Controls the test cases Stub: A component, the Tested. Unit depends on Partial implementation Returns fake values. Tested Unit Stub
![EXAMPLE THREE LAYER CALL HIERARCHY A C B E Layer I F D EXAMPLE : THREE LAYER CALL HIERARCHY A C B E Layer I F D](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-16.jpg)
EXAMPLE : THREE LAYER CALL HIERARCHY A C B E Layer I F D Layer II G Layer III
![INTEGRATION TESTING BIGBANG APPROACH INTEGRATION TESTING: BIGBANG APPROACH](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-17.jpg)
INTEGRATION TESTING: BIGBANG APPROACH
![BOTTOMUP INTEGRATION BOTTOM-UP INTEGRATION](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-18.jpg)
BOTTOM-UP INTEGRATION
![PROS AND CONS OF BOTTOM UP INTEGRATION TESTING Bad for functionally decomposed systems Tests PROS AND CONS OF BOTTOM UP INTEGRATION TESTING Bad for functionally decomposed systems: Tests](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-19.jpg)
PROS AND CONS OF BOTTOM UP INTEGRATION TESTING Bad for functionally decomposed systems: Tests the most important subsystem (UI) last Useful for integrating the following systems Object-oriented systems real-time systems with strict performance requirements
![TOPDOWN INTEGRATION TESTING TOP-DOWN INTEGRATION TESTING](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-20.jpg)
TOP-DOWN INTEGRATION TESTING
![PROS AND CONS OF TOPDOWN INTEGRATION TESTING q Test cases can be defined in PROS AND CONS OF TOP-DOWN INTEGRATION TESTING q. Test cases can be defined in](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-21.jpg)
PROS AND CONS OF TOP-DOWN INTEGRATION TESTING q. Test cases can be defined in terms of the functionality of the system (functional requirements) q. Writing stubs can be difficult: Stubs must allow all possible conditions to be tested. q. 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
![SANDWICH TESTING STRATEGY Combines topdown strategy with bottomup strategy The system is view as SANDWICH TESTING STRATEGY Combines top-down strategy with bottom-up strategy The system is view as](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-22.jpg)
SANDWICH TESTING STRATEGY Combines top-down strategy with bottom-up strategy The system is view as having three layers 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? Heuristic: Try to minimize the number of stubs and drivers
![SANDWICH TESTING STRATEGY SANDWICH TESTING STRATEGY](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-23.jpg)
SANDWICH TESTING STRATEGY
![PROS AND CONS OF SANDWICH TESTING v Top and Bottom Layer Tests can be PROS AND CONS OF SANDWICH TESTING v. Top and Bottom Layer Tests can be](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-24.jpg)
PROS AND CONS OF SANDWICH TESTING v. Top and Bottom Layer Tests can be done in parallel v. Does not test the individual subsystems thoroughly before integration v. Solution: Modified sandwich testing strategy
![MODIFIED SANDWICH TESTING STRATEGY Test in parallel Middle layer with drivers and stubs Top MODIFIED SANDWICH TESTING STRATEGY Test in parallel: Middle layer with drivers and stubs Top](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-25.jpg)
MODIFIED SANDWICH TESTING STRATEGY Test in parallel: Middle layer with drivers and stubs Top layer with stubs Bottom layer with drivers Test in parallel: Top layer accessing middle layer (top layer replaces drivers) Bottom accessed by middle layer (bottom layer replaces stubs)
![MODIFIED SANDWICH TESTING STRATEGY MODIFIED SANDWICH TESTING STRATEGY](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-26.jpg)
MODIFIED SANDWICH TESTING STRATEGY
![STEPS IN INTEGRATIONTESTING 1 Based on the integration strategy select a component to be STEPS IN INTEGRATIONTESTING 1. Based on the integration strategy, select a component to be](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-27.jpg)
STEPS IN INTEGRATIONTESTING 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.
![WHICH INTEGRATION STRATEGY SHOULD YOU USE w Toplevel components are usually important WHICH INTEGRATION STRATEGY SHOULD YOU USE? w. . . Top-level components are usually important](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-28.jpg)
WHICH INTEGRATION STRATEGY SHOULD YOU USE? w. . . Top-level components are usually important and cannot be neglected up to the end of testing w Detection of design errors postponed until end of testing ¨ Top down approach w Test cases can be defined in terms of functions examined w Need to maintain correctness of test stubs w Writing stubs can be difficult ¨ Factors to consider w Amount of test harness (stubs &drivers) w Location of critical parts in the system w Availability of hardware w Availability of components w Scheduling concerns ¨ Bottom up approach w good for object oriented design methodologies w Test driver interfaces must match component interfaces w. . .
![SYSTEM TESTING Functional Testing Structure Testing Performance Testing Acceptance Testing Installation Testing Impact of SYSTEM TESTING §Functional Testing §Structure Testing §Performance Testing §Acceptance Testing §Installation Testing Impact of](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-29.jpg)
SYSTEM TESTING §Functional Testing §Structure Testing §Performance Testing §Acceptance Testing §Installation Testing Impact of requirements on system testing: The more explicit the requirements, the easier they are to test. Quality of use cases determines the ease of functional testing Quality of subsystem decomposition determines the ease of structure testing Quality of nonfunctional requirements and constraints determines the ease of performance tests
![STRUCTURE TESTING Essentially the same as white box testing Goal Cover all paths in STRUCTURE TESTING Essentially the same as white box testing. Goal: Cover all paths in](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-30.jpg)
STRUCTURE TESTING Essentially the same as white box testing. Goal: Cover all paths in the system design Exercise all input and output parameters of each component. Exercise all components and all calls (each component is called at least once and every component is called by all possible callers. ) Use conditional and iteration testing as in unit testing.
![FUNCTIONAL TESTING Essentially the same as black box testing Goal Test functionality FUNCTIONAL TESTING Essentially the same as black box testing ¨ ¨ Goal: Test functionality](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-31.jpg)
FUNCTIONAL TESTING Essentially the same as black box testing ¨ ¨ Goal: Test functionality of system Test cases are designed from the requirements analysis document (better: user manual) and centered around requirements and key functions (use cases) The system is treated as black box. Unit test cases can be reused, but in end user oriented new test cases have to be developed as well.
![PERFORMANCE TESTING Stress Testing w Stress limits of system maximum of users PERFORMANCE TESTING ¨ Stress Testing w Stress limits of system (maximum # of users,](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-32.jpg)
PERFORMANCE TESTING ¨ Stress Testing w Stress limits of system (maximum # of users, peak demands, extended operation) ¨ ¨ Security testing w Try to violate security requirements Environmental test w Test tolerances for heat, humidity, motion, portability ¨ Quality testing w Test reliability, maintain- ability & availability of the system ¨ Compatibility test w Test backward compatibility with existing systems ¨ ¨ Configuration testing w Test the various software and hardware configurations Timing testing w Evaluate response times and time to perform a function Volume testing w Test what happens if large amounts of data are handled ¨ ¨ Recovery testing w Tests system’s response to presence of errors or loss of data. ¨ Human factors testing w Tests user interface with user
![TEST CASES FOR PERFORMANCE TESTING Push the integrated system to its TEST CASES FOR PERFORMANCE TESTING ¨ ¨ ¨ Push the (integrated) system to its](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-33.jpg)
TEST CASES FOR PERFORMANCE TESTING ¨ ¨ ¨ Push the (integrated) system to its limits. Goal: Try to break the subsystem Test how the system behaves when overloaded. w Can bottlenecks be identified? (First candidates for redesign in the next iteration ¨ Try unusual orders of execution w Call a receive() before send() ¨ Check the system’s response to large volumes of data w If the system is supposed to handle 1000 items, try it with 1001 items. ¨ What is the amount of time spent in different use cases? w Are typical cases executed in a timely fashion?
![ACCEPTANCE TESTING Goal Demonstrate system is ready for operational use Alpha ACCEPTANCE TESTING ¨ ¨ Goal: Demonstrate system is ready for operational use ¨ Alpha](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-34.jpg)
ACCEPTANCE TESTING ¨ ¨ Goal: Demonstrate system is ready for operational use ¨ Alpha test: w Choice of tests is made by client/sponsor w Many tests can be taken from integration testing w Acceptance test is performed by the client, not by the developer. Majority of all bugs in software is typically found by the client after the system is in use, not by the developers or testers. Therefore two kinds of additional tests: ¨ Beta test: w Conducted at sponsor’s site w Sponsor uses the software at the developer’s site. w Software used in a controlled setting, with the developer always ready to fix bugs. (developer is not present) w Software gets a realistic workout in target environ- ment w Potential customer might get discouraged
![TESTING LIFE CYCLE TESTING LIFE CYCLE](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-35.jpg)
TESTING LIFE CYCLE
![TEST TEAM TEST TEAM](https://slidetodoc.com/presentation_image_h2/45951b7adb0e8cfdc85d14ad0277820c/image-36.jpg)
TEST TEAM
Object oriented system testing
Forward integration and backward integration
Vertical integration
Simultaneous integration meaning
System integration testing checklist
Unit 10, unit 10 review tests, unit 10 general test
Functional testing vs unit testing
Big bang approach in testing
The joint capabilities integration and development system
The joint capabilities integration and development system
Joint capabilities integration and development system
"data integration"
Se 465
Sandwich integration testing
Neighborhood integration testing
Call graph based integration in software testing
Integration testing
Integration testing software engineering
Bottom up integration testing
Sandwich integration testing
Airflow ci cd
Is earth a closed system or open system
Respiratory digestive and circulatory system
System integration life cycle
System integration plan
Horizontal silos in system integration
System integration life cycle
Validated system integration
System integration methods
System center orchestrator integration packs
Horizontal system integration
Enterprise integration pattern
Hyp opp adj triangle
Unit process and unit operation
Difference between unit process and unit operation
Unit xi testing and individual differences
Positive testing vs negative testing