Which testing level focuses on the interaction between modules?

Which testing level focuses on the interaction between modules?

• A. Unit
• B. Integration
• C. Module
• D. System

Answer: (B)

The focus here is on how different parts of a system work together. When you test a single component in isolation to confirm it behaves correctly on its own, that’s unit testing. To ensure that multiple modules interact properly—that data and control pass correctly across boundaries, interfaces are respected, and dependencies behave as expected—you test at the integration level. In a healthcare information system, this means checking that information flows correctly between modules, such as patient data moving from the registration module to the scheduling or billing modules, and that shared data remains consistent and correctly formatted as it traverses interfaces. System testing would validate the whole system end-to-end, while unit or module-focused testing wouldn’t primarily address cross-module interactions. So, the level that concentrates on the interaction between modules is integration testing.

The focus here is on how different parts of a system work together. When you test a single component in isolation to confirm it behaves correctly on its own, that’s unit testing. To ensure that multiple modules interact properly—that data and control pass correctly across boundaries, interfaces are respected, and dependencies behave as expected—you test at the integration level. In a healthcare information system, this means checking that information flows correctly between modules, such as patient data moving from the registration module to the scheduling or billing modules, and that shared data remains consistent and correctly formatted as it traverses interfaces. System testing would validate the whole system end-to-end, while unit or module-focused testing wouldn’t primarily address cross-module interactions. So, the level that concentrates on the interaction between modules is integration testing.