Microservices Testing Strategies for Microservices 3

Question 1

Which testing pattern involves deploying two identical environments and switching traffic between them to enable zero-downtime deployments and easy rollback?

Accepted Answer

Blue-green deployment

Answer

Canary deployment

Answer

Rolling deployment

Answer

Shadow deployment

Question 2

What is 'property-based testing' and how does it benefit microservices?

Accepted Answer

Automatically generating a wide range of inputs to verify that service properties hold true across all of them

Answer

Testing only the public properties of service objects

Answer

Checking that service configurations match expected property files

Answer

Testing services based on their OpenAPI property definitions

Question 3

In microservices testing, what problem does the 'test environment parity' principle address?

Accepted Answer

Ensuring test environments closely match production to avoid 'works on my machine' failures

Answer

Making sure all microservices have the same number of tests

Answer

Keeping test execution times equal across services

Answer

Ensuring all developers run the same number of tests locally

Question 4

What is a 'test harness' in the context of microservices integration testing?

Accepted Answer

A framework or set of utilities that manages test doubles, setup, and teardown for service integration tests

Answer

A CI/CD pipeline configuration file

Answer

A load testing tool that simulates concurrent users

Answer

A security scanner integrated into the test pipeline

Question 5

When testing asynchronous microservices that communicate via message queues, which approach is most effective for verifying correct behavior?

Accepted Answer

Use polling or await mechanisms to verify that expected messages are produced or consumed within a timeout

Answer

Mock the message queue and test synchronously

Answer

Only test synchronous fallback paths

Answer

Test using direct database queries instead of the queue

Question 6

What is 'chaos engineering' and how does it relate to testing microservices?

Accepted Answer

Deliberately injecting failures (latency, errors, crashes) into a system to verify it handles them gracefully

Answer

Writing tests in random order to find ordering dependencies

Answer

Removing all test environments and deploying directly to production

Answer

Testing microservices with randomized API inputs

Question 7

Which testing strategy is recommended when a microservice has been modified and you want to ensure no existing functionality was broken, without re-writing all tests?

Accepted Answer

Regression testing

Answer

Mutation testing

Answer

Exploratory testing

Answer

Property-based testing