Which approach supports swapping implementations at runtime to ease testing?

Which approach supports swapping implementations at runtime to ease testing?

• A. Dependency injection via interfaces
• B. Hard-coded dependencies
• C. Static binding
• D. Global variables

Answer: (A)

Swapping implementations at runtime to ease testing relies on decoupling a component from concrete classes and depending on an abstraction such as an interface. With dependency injection, the outside code provides the actual implementation to use, typically through the constructor, setter, or a factory. Because the component code depends on an interface rather than a concrete type, you can plug in a mock or stub during tests without modifying production code. At runtime, the real implementation is bound in the normal application flow, while tests bind a test double, giving you fast, isolated tests and more flexible test scenarios. In contrast, hard-coded dependencies embed the concrete class inside the consumer, making runtime swaps impossible. Static binding fixes the implementation at load time, so substitutes can't be provided without changing code. Global variables introduce shared mutable state and coupling, which makes swapping implementations brittle and hard to manage.

Swapping implementations at runtime to ease testing relies on decoupling a component from concrete classes and depending on an abstraction such as an interface. With dependency injection, the outside code provides the actual implementation to use, typically through the constructor, setter, or a factory. Because the component code depends on an interface rather than a concrete type, you can plug in a mock or stub during tests without modifying production code. At runtime, the real implementation is bound in the normal application flow, while tests bind a test double, giving you fast, isolated tests and more flexible test scenarios. In contrast, hard-coded dependencies embed the concrete class inside the consumer, making runtime swaps impossible. Static binding fixes the implementation at load time, so substitutes can't be provided without changing code. Global variables introduce shared mutable state and coupling, which makes swapping implementations brittle and hard to manage.