In context of software testing match of Column-I and Column-II is:
Column-I - Column-II
i. Integration Testing - a. Alpha Testing
ii. Unit Testing - b. Usability Testing,
iii. Acceptance Testing - c. Data Flow Testing
iv. System Testing - d. Black Box Testing.

Question

In context of software testing match of Column-I and Column-II is: 
Column-I - Column-II
i. Integration Testing - a. Alpha Testing
ii. Unit Testing - b. Usability Testing,
iii. Acceptance Testing -  c. Data Flow Testing
iv. System Testing - d. Black Box Testing.

Accepted Answer

The correct option is (3):
The correct pairing for these testing types and their associated concepts is i-c, ii-d, iii-a, and iv-b, which reflects their typical placement and methodology in the software development lifecycle. Acceptance Testing (iii) is a formal testing process to determine if the system meets the customer’s requirements, and a common form of this is Alpha Testing (a), which is conducted internally by the development team. System Testing (iv) validates the fully integrated software against the system's specifications, including non-functional requirements like performance and Usability Testing (b). For the remaining pairs, Data Flow Testing (c) is a technique for verifying data handling and transformations, which is critical for checking the interaction and flow *between* modules in Integration Testing (i). Finally, while Unit Testing (ii) is often white-box, it can be approached using Black Box Testing (d) by simply checking the module's public interface and functionality against its specification without examining the internal code.

The incorrect option is (1):
This option states that Integration Testing is Alpha Testing (i-a) and Unit Testing is Usability Testing (ii-b), both of which are fundamentally wrong. Alpha testing is a *type* of Acceptance Testing (iii), and Integration testing operates on groups of modules, not the final user acceptance. Similarly, Usability testing is a *non-functional* test that occurs at the System Testing level (iv), while Unit Testing focuses on the functional correctness of a single, smallest component of code. The combination iii-d and iv-c are also misplaced, as Black Box testing (d) is an approach that can be applied to many levels, and Data Flow Testing (c) is a technique, not a final test phase.

The incorrect option is (2):
This option pairs Acceptance Testing with Usability Testing (iii-b) and System Testing with Alpha Testing (iv-a), incorrectly swapping two major test categories. Alpha Testing (a) is definitively a type of Acceptance Test (iii) aimed at final sign-off. Usability Testing (b) is a non-functional test carried out during the System Testing phase (iv) to ensure the product is user-friendly. Furthermore, while the pairing of Integration Testing with Black Box Testing (i-d) and Unit Testing with Data Flow Testing (ii-c) are plausible testing strategies, the significant error in miscategorizing the final-stage testing types makes this option incorrect overall.

The incorrect option is (4):
The primary flaw in this option is matching Integration Testing with Usability Testing (i-b) and System Testing with Data Flow Testing (iv-c). Usability Testing (b) is a non-functional test that belongs to the overall System Testing (iv). Conversely, Data Flow Testing (c) is a specific white-box *technique* applied to scrutinize the logic and data flow within a module or a small group of modules, making it suitable for Unit or Integration Testing, not the comprehensive system level. The pair ii-d (Unit Testing-Black Box Testing) and iii-a (Acceptance Testing-Alpha Testing) are acceptable matches, but the errors in the other two pairings invalidate this option.