Which is not the right approach of incremental testing approach?

Question

Accepted Answer

The correct option is (1):
The core philosophy of incremental testing is to integrate and test modules step-by-step, or in small, logical groupings, allowing defects to be found early and easily isolated to the most recently added module. The **Big Bang approach** fundamentally violates this principle. In Big Bang testing, all individual, unit-tested modules are completely assembled and integrated *at once*, and only then is the entire system tested as a single entity. Because this method skips the gradual, progressive integration phase, it is classified as a non-incremental approach to integration testing, and is therefore the answer to the question of which approach is *not* incremental.

The incorrect option is (2):
The Top-down approach is a classic form of **incremental testing**. In this technique, testing starts with the main control module (the 'top') and proceeds downwards. Lower-level modules that are not yet developed are simulated using temporary programs called **stubs**. The process involves integrating one module at a time into the existing tested structure, which is the very definition of an incremental strategy.

The incorrect option is (3):
The option "Functional incrimination" is a known clerical error for **Functional Increment** or **Functional Integration**. This is a recognized approach to **incremental testing** where modules are grouped and integrated based on a complete, demonstrable functional requirement or use case. This step-by-step integration of features ensures that the system's core capabilities are tested early and progressively, aligning perfectly with the goals of an incremental testing methodology.

The incorrect option is (4):
The Bottom-up approach is a standard and effective type of **incremental testing**. It starts with the lowest-level utility modules (the 'bottom') which are integrated and tested first. Higher-level calling modules, which are not yet complete, are simulated using test programs called **drivers**. Modules are integrated progressively from the bottom up, one layer at a time, making it a clear example of an incremental integration strategy.