concept canned response in category microservice

This is an excerpt from Manning's book Testing Microservices with Mountebank.
Service virtualization involves nothing more than using test doubles that operate over the wire and is analogous to how you test car batteries without a real alternator. You silo the runtime environment into the bits relevant to test a single service or application and fake the rest, assuming standard interfaces. In traditional mocking and stubbing libraries, you would stub out a dependency and inject that into your object’s constructor, allowing your tests to probe the object under test in isolation. With service virtualization, you virtualize a service and configure the service under test to use the virtualized service’s URL as a runtime dependency (figure 1.9). You can set up the virtual service with a specific set of canned responses, allowing you to probe the service under test in isolation.
In mountebank, the is response type is how you create canned responses, or responses that simulate a real response in some static way that you configure. Although it is one of three response types (proxy and inject being the other two), it’s the most important one. In this chapter, we will explore is responses both by using the REST API and by persisting them in configuration files.