Integration and System Testing SE Unit-4 Part-4.pdf
- 1. 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. • Integration testing is a software testing technique that focuses on verifying the interactions and data exchange between different components or modules of a software application. • The goal of integration testing is to identify any problems or bugs that arise when different components are combined and interact with each other. Integration testing is typically performed after unit testing and before system testing. • Exposing the defects is the major focus of the integration testing and the time of interaction between the integrated units.
- 2. Applications of Integration Testing 1. Identify the components: Identify the individual components of your application that need to be integrated. This could include the frontend, backend, database, and any third-party services. 2. Create a test plan: Develop a test plan that outlines the scenarios and test cases that need to be executed to validate the integration points between the different components. This could include testing data flow, communication protocols, and error handling. 3. Set up test environment: Set up a test environment that mirrors the production environment as closely as possible. This will help ensure that the results of your integration tests are accurate and reliable. 4. Execute the tests: Execute the tests outlined in your test plan, starting with the most critical and complex scenarios. Be sure to log any defects or issues that you encounter during testing. 5. Analyze the results: Analyze the results of your integration tests to identify any defects or issues that need to be addressed. This may involve working with developers to fix bugs or make changes to the application architecture. 6. Repeat testing: Once defects have been fixed, repeat the integration testing process to ensure that the changes have been successful and that the application still works as expected.
- 3. Test Cases For Integration Testing • Interface Testing : Verify that data exchange between modules occurs correctly. Validate input/output parameters and formats. Ensure proper error handling and exception propagation between modules. • Functional Flow Testing : Test end-to-end functionality by simulating user interactions. Verify that user inputs are processed correctly and produce expected outputs. Ensure seamless flow of data and control between modules. • Data Integration Testing : Validate data integrity and consistency across different modules. Test data transformation and conversion between formats. Verify proper handling of edge cases and boundary conditions. • Dependency Testing : Test interactions between dependent modules. Verify that changes in one module do not adversely affect others. Ensure proper synchronization and communication between modules.
- 4. • Error Handling Testing : Validate error detection and reporting mechanisms. Test error recovery and fault tolerance capabilities. Ensure that error messages are clear and informative. • Performance Testing : Measure system performance under integrated conditions. Test response times, throughput, and resource utilization. Verify scalability and concurrency handling between modules. • Security Testing : Test access controls and permissions between integrated modules. Verify encryption and data protection mechanisms. Ensure compliance with security standards and regulations. • Compatibility Testing : Test compatibility with external systems, APIs, and third-party components. Validate interoperability and data exchange protocols. Ensure seamless integration with different platforms and environments.
- 5. S. No. Unit Testing Integration Testing 1. In unit testing, each module of the software is tested separately. In integration testing, all modules of the software are tested combined. 2. In unit testing tester knows the internal design of the software. Integration testing doesn’t know the internal design of the software. 3. Unit testing is performed first of all testing processes. Integration testing is performed after unit testing and before system testing. 4. Unit testing is white box testing. Integration testing is black box testing. 5. Unit testing is performed by the developer. Integration testing is performed by the tester.
- 6. System Testing • 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 is performed after the integration testing and before the acceptance testing. • System Testing is a type of software testing that is performed on a completely integrated system to evaluate the compliance of the system with the corresponding requirements. In system testing, integration testing passed components are taken as input. • System testing detects defects within both the integrated units and the whole system. • The result of system testing is the observed behavior of a component or a system when it is tested.
- 7. • System Testing is carried out on the whole system in the context of either system requirement specifications or functional requirement specifications or the context of both. • System testing tests the design and behavior of the system and also the expectations of the customer. • It is performed to test the system beyond the bounds mentioned in the software requirements specification (SRS) . • System Testing is performed by a testing team that is independent of the development team and helps to test the quality of the system impartial. • It has both functional and non-functional testing. System Testing is a black-box testing . System Testing is performed after the integration testing and before the acceptance testing.
- 10. System Testing Process • Test Environment Setup: Create testing environment for the better quality testing. • Create Test Case: Generate test case for the testing process. • Create Test Data: Generate the data that is to be tested. • Execute Test Case: After the generation of the test case and the test data, test cases are executed. • Defect Reporting: Defects in the system are detected. • Regression Testing: It is carried out to test the side effects of the testing process. • Log Defects: Defects are fixed in this step. • Retest: If the test is not successful then again test is performed.
- 11. Types of System Testing 1. Performance Testing: Performance Testing is a type of software testing that is carried out to test the speed, scalability, stability and reliability of the software product or application. 2. Load Testing: Load Testing is a type of software Testing which is carried out to determine the behavior of a system or software product under extreme load. 3. Stress Testing: Stress Testing is a type of software testing performed to check the robustness of the system under the varying loads. 4. Scalability Testing: Scalability Testing is a type of software testing which is carried out to check the performance of a software application or system in terms of its capability to scale up or scale down the number of user request load.
- 12. Tools used for System Testing 1.JMeter 2.Gallen Framework 3.HP Quality Center/ALM 4.IBM Rational Quality Manager 5.Microsoft Test Manager 6.Selenium 7.Appium 8.LoadRunner 11.Apache JServ 12.SoapUI
- 13. Advantages of System Testing • The testers do not require more knowledge of programming to carry out this testing. • It will test the entire product or software so that we will easily detect the errors or defects which cannot be identified during the unit testing and integration testing. • The testing environment is similar to that of the real time production or business environment. • It checks the entire functionality of the system with different test scripts and also it covers the technical and business requirements of clients. • After this testing, the product will almost cover all the possible bugs or errors and hence the development team will confidently go ahead with acceptance testing • Verifies the overall functionality of the system. • Detects and identifies system-level problems early in the development cycle.
- 14. Disadvantages of System Testing • This testing is time consuming process than another testing techniques since it checks the entire product or software. • The cost for the testing will be high since it covers the testing of entire software. • It needs good debugging tool otherwise the hidden errors will not be found. • Can be time-consuming and expensive. • Requires adequate resources and infrastructure. • Can be complex and challenging, especially for large and complex systems. • Dependent on the quality of requirements and design documents. • Limited visibility into the internal workings of the system.