System testing in software engineering.pptx
Download as PPTX, PDF0 likes112 views
The document provides an overview of system testing, detailing its importance in evaluating the functionality and performance of integrated software. It covers different types of integration testing—bottom-up, top-down, and mixed—along with their advantages and disadvantages, as well as acceptance testing, which ensures software meets user needs and business requirements. Ultimately, it emphasizes the importance of user involvement in the testing process to enhance product quality and performance.
System testing in software engineering.pptx
- 1. System Testing Mrs.G.Chandraprabha., M.Sc., M.Phil., Assistant Professor of IT, V.V.Vanniaperumal College for Women, Virudhunagar.
- 2. System Testing-Introduction System testing is a type of software testing that evaluates the overall functionality and performance of a complete and fully integrated software solution. It tests if the system meets the specified requirements and if it is suitable for delivery to the end-users. This type of testing Includes two kinds of activities, the integration testing and the acceptance testing.
- 3. Integration Testing Integration testing is the process of testing the interface between two software units or modules. It focuses on determining the correctness of the interface. The purpose of integration testing is to expose faults in the interaction between integrated units. Once all the modules have been unit-tested, integration testing is performed.
- 4. Types of Integration Testing Depending on the functionality, Integration testing is divided into three types. Bottom-Up Integration Testing Top-down Integration Testing Mixed Integration Testing
- 5. Bottom-Up Integration testing In bottom-up testing, each module at lower levels are tested with higher modules until all modules are tested. The primary purpose of this integration testing is that each subsystem tests the interfaces among various modules making up the subsystem. This integration testing uses test drivers to drive and pass appropriate data to the lower-level modules.
- 6. Advantages of Bottom-Up Integration testing In bottom-up testing, no stubs are required. A principal advantage of this integration testing is that several disjoint subsystems can be tested simultaneously. It is easy to create the test conditions. Best for applications that uses bottom up design approach. It is Easy to observe the test results.
- 7. Disadvantages of Bottom-Up Integration testing Driver modules must be produced. In this testing, the complexity that occurs when the system is made up of a large number of small subsystems. As Far modules have been created, there is no working model can be represented.
- 8. Top-Down Integration testing Top-down integration testing technique is used in order to simulate the behaviour of the lower-level modules that are not yet integrated. In this integration testing, testing takes place from top to bottom. First, high-level modules are tested and then low-level modules and finally integrating the low-level modules to a high level to ensure the system is working as intended.
- 9. Advantages of Top-Down Integration testing Separately debugged module. Few or no drivers needed. It is more stable and accurate at the aggregate level. Easier isolation of interface errors. In this, design defects can be found in the early stages.
- 10. Disadvantages of Top-Down Integration testing Needs many Stubs. Modules at lower level are tested inadequately. It is difficult to observe the test output. It is difficult to stub design.
- 11. Mixed Integration testing A mixed integration testing is also called sandwiched integration testing. A mixed integration testing follows a combination of top down and bottom-up testing approaches. In top-down approach, testing can start only after the top-level module have been coded and unit tested. In bottom-up approach, testing can start only after the bottom level modules are ready.
- 12. Mixed Integration testing This sandwich or mixed approach overcomes this shortcoming of the top-down and bottom-up approaches. It is also called the hybrid integration testing. stubs and drivers are used in mixed integration testing.
- 13. Advantages of Mixed Integration testing Mixed approach is useful for very large projects having several sub projects. This Sandwich approach overcomes this shortcoming of the top-down and bottom-up approaches. Parallel test can be performed in top and bottom layer tests.
- 14. Disadvantages of Mixed Integration testing For mixed integration testing, it requires very high cost because one part has a Top- down approach while another part has a bottom-up approach. This integration testing cannot be used for smaller systems with huge interdependence between different modules.
- 15. Acceptance Testing Acceptance Testing is an important aspect of Software Testing, which guarantees that software aligns with user needs and business requirements. The major aim of this test is to evaluate the compliance of the system with the business requirements and assess whether it is acceptable for delivery or not.
- 16. Use of Acceptance Testing To find the defects missed during the functional testing phase. How well the product is developed. A product is what actually the customers need. Feedback help in improving the product performance and user experience. Minimize or eliminate the issues arising from the production.
- 17. Advantages of Acceptance Testing This testing helps the project team to know the further requirements from the users directly as it involves the users for testing. Automated test execution. It brings confidence and satisfaction to the clients as they are directly involved in the testing process. It is easier for the user to describe their requirement. It covers only the Black-Box testing process and hence the entire functionality of the product will be tested.
- 18. Thank You