Beyond simple mocking, what is 'Service Virtualization' and how can it be used to create more realistic integration tests for a Node.js application that depends on third-party APIs?
Node.js interview question for Advanced practice.
Answer
Service virtualization is the practice of creating a 'virtual' or simulated test environment that mimics the behavior of a real external dependency, such as a third-party API. Unlike simple library mocks that replace a module within your application's code, a virtualized service is a separate, running server that your application communicates with over the network, just as it would with the real service. How it works: You would use a tool like Mountebank to create a standalone server. In your tests, you configure this server to listen for specific requests (e.g., GET /api/v1/products/123) and respond with predefined data, status codes, and headers. Your Node.js application is then configured (e.g., via an environment variable) to point to the virtual service's URL instead of the real API's URL. Advantages over simple mocking: Higher Fidelity: It tests the entire network stack of your application (HTTP requests, serialization/deserialization, error handling over the network), which simple mocks bypass. Realism: It can simulate real-world conditions that mocks cannot, such as network latency, rate limiting, and specific error codes (like 502 Bad Gateway). Reusability: The virtualized service can be shared by multiple teams and used for different types of testing, not just integration tests.
Explanation
Tools like Mountebank and WireMock are popular open-source options for implementing service virtualization.