An organization is writing its test strategy in order to define the test levels and test types that are in scope for testing. In the past, the organization has experienced service disruptions after…

The correct answer is B. Integration. Integration testing directly targets the interactions between applications - exactly the failure mode described. When application A causes application B to generate errors after a release, that's a boundary/interface problem, not an internal logic problem. Integration tests…

Understand how relevant ITIL practices contribute to creation, delivery and support across the SVS and value streams

Question

An organization is writing its test strategy in order to define the test levels and test types that are in scope for testing. In the past, the organization has experienced service disruptions after some releases of a particular application. These disruptions were happening because the application caused other applications to generate errors. Which test level should the organization focus on to address this weakness?

Options

AUnit
BIntegration
CSystem
DAcceptance

How the community answered

(33 responses)

A
12% (4)
B
79% (26)
C
6% (2)
D
3% (1)

Explanation

Integration testing directly targets the interactions between applications - exactly the failure mode described. When application A causes application B to generate errors after a release, that's a boundary/interface problem, not an internal logic problem. Integration tests verify that components and systems communicate correctly with each other, catching these cross-application defects before they reach production.

Why the others are wrong:

A (Unit): Unit tests validate isolated code units in isolation - they can't detect how one application affects another.
C (System): System testing validates a single system end-to-end against requirements; it doesn't specifically target inter-application interactions.
D (Acceptance): Acceptance testing confirms the system meets business/user needs - it's about fitness for purpose, not diagnosing cross-system failures.

Memory tip: Think of "Integration" as testing the handshakes between systems. If the bug lives inside one app → Unit. If it lives between apps → Integration. If the organization's pain is "our app breaks other apps," the problem is in that handshake.

Topics

#service validation and testing#integration testing#test levels#test strategy

Community Discussion

No community discussion yet for this question.

Full ITIL-4-CDS Practice