Progressive Testing Approaches
- Bottom-up approach – In the Bottom-up approach all components are combined one by one from bottom level to top level until all components are integrated.
- Top-down approach – In Top top-down approach all components are combined one by one from the top level to the bottom level until all components are integrated. Stubs are used to replace the need for essential components.
- Functional approach – In the Functional approach testing is carried out horizontally means integration is done based on functionality. That’s why it is also named Functional Increment.
- Hybrid approach – In the Hybrid approach both the top-down approach and with Bottom approach are followed. In this, we exploit the advantages of both the Top-down approach and the Bottom-up approach.
Progressive Testing in Software Testing
Progressive Testing is also known as Incremental Testing. In Software Testing Incremental Testing refers to test modules one after another. When in an application parent-child modules are tested related modules need to be tested first.
Let’s understand Progressive Testing/Increment Testing more elaborately by going a little bit deeper into it. This Increment Testing is considered a sub-testing technique that comes under Integration Testing. This testing acts as an approach/strategy to perform integration testing on software products rather than direct testing activities.
After completion of Unit Testing over each component of the software, then Integration Testing is performed to ensure proper interface and interaction between components of the system. Incremental testing or Progressive testing is treated as a partial phase of Integration testing. First, it performs Integration testing on standalone components thereafter it goes on integrating components and performs integration testing over them accordingly. As the components are integrated in an incremental manner that’s why also it is termed Incremental Testing.