QAs testing microservices can use third party and backend mocks to speed up testing

While testing microservices you will often need to mock or stub the third-party and legacy backend systems.

Third-party and backend system mocks and stubs will help you resolve issues with:

* Setting up test data in third party and backend systems

* Simulating API and backend system error messages (for negative or sad path testing)

* Simulating protocol-specific errors (for negative or sad path testing)

* Simulating slow responses (for performance testing)

You can create HTTP, gRPC, JMS IBM MQ and other types of mocks with Traffic Parrot.

You can run Traffic Parrot in Docker and OpenShift and Kubernetes, which is what you need when working with microservice architectures.

For more details how to use mocks when testing microservices watch "How software testers can test microservices".

See the diagram below for example usage of Traffic Parrot when testing microservices: