Software Testing: A Guide to Unit, Integration, System, and Regression Testing, Slides of Software Engineering

Download Software Testing: A Guide to Unit, Integration, System, and Regression Testing and more Slides Software Engineering in PDF only on Docsity!

What is debugging

• Debugging is the process of finding and resolving defects or problems within a computer program that prevent correct operation of computer software or a system

Unit Testing

• During this first round of testing, the program is submitted to assessments that focus on specific units or components of the software to determine whether each one is fully functional.
• The main aim of this endeavor is to determine whether the application functions as designed.
• In this phase, a unit can refer to a function, individual program or even a procedure, and a White-box Testing method is usually used to get the job done.
• One of the biggest benefits of this testing phase is that it can be run every time a piece of code is changed, allowing issues to be resolved as quickly as possible.

Integration Testing

• Integration testing allows individuals the opportunity to combine all of the units within a program and test them as a group. - This testing level is designed to find interface defects between the modules/functions.
• This is particularly beneficial because it determines how efficiently the units are running together.
• Keep in mind that no matter how efficiently each unit is running, if they aren’t properly integrated, it will affect the functionality of the software program.

Big Bang and Top Down

• Big Bang is an approach to Integration Testing where all or most f the units are combined together and tested at one go. This approach is taken when the testing team receives the entire software in a bundle. So what is the difference between Big Bang Integration Testing and System Testing? Well, the former tests only the interactions between the units while the latter tests the entire system.
• Top Down is an approach to Integration Testing where top-level units are tested first and lower level units are tested step by step after that. This approach is taken when top-down development approach is followed. Test Stubs are needed to simulate lower level units which may not be available during the initial phases.

Bottom up and Hybrid

- Bottom Up is an approach to Integration Testing where bottom level units are tested first and upper-level units step by step after that. This approach is taken when bottom-up development approach is followed. Test Drivers are needed to simulate higher level units which may not be available during the initial phases. - Sandwich/Hybrid is an approach to Integration Testing which is a combination of Top Down and Bottom Up approaches.

System Testing

• System testing is the first level in which the complete application is tested as a whole. - The goal at this level is to evaluate whether the system has complied with all of the outlined requirements and to see that it meets Quality Standards.
• System testing is undertaken by independent testers who haven’t played a role in developing the program.
• This testing is performed in an environment that closely mirrors production.
• System Testing is very important because it verifies that the application meets the technical, functional, and business requirements that were set by the customer.

Regression testing

• Regression testing is the process of testing changes to computer programs to make sure that the older programming still works with the new changes.
• Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists.

Test Levels

• Unit Testing - done by developers
• Integration Testing - done by QA team
• System testing - done by QA team
• Acceptance Testing - Done by customers