Contract testing (Pact) in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the Purpose of Contract Testing with Pact

Which of the following best describes the primary purpose of using Pact in microservices?

A To monitor live traffic between microservices in production environments.

B To perform load testing on microservices to check their performance under stress.

C To automate UI testing of microservices' front-end interfaces.

D To verify that the interactions between a service consumer and provider meet a shared contract without deploying the services.

💡 Hint

Think about what contract testing ensures between two services before they communicate.

Pact is used to verify that the consumer and provider agree on the API contract, ensuring compatibility without needing to deploy both services together.

❓ Architecture

intermediate

Key Components in a Pact Contract Testing Setup

Which component is responsible for generating the contract file in a Pact testing setup?

A The API gateway generates the contract by intercepting traffic.

B The service provider publishes the contract after running its tests.

C The service consumer generates the contract during its tests.

D A separate contract registry automatically creates contracts from API definitions.

💡 Hint

Consider which side defines the expected interactions first.

The consumer writes tests that define expected requests and responses, generating the Pact contract file used to verify the provider.

❓ scaling

advanced

Scaling Contract Testing in a Large Microservices Environment

In a system with 50 microservices, each with multiple consumers and providers, what is the best approach to manage Pact contract testing efficiently?

A Skip contract testing for less critical services to reduce overhead.

B Centralize all contracts in a shared Pact Broker and automate verification pipelines for each service.

C Each team manually shares contract files via email and runs tests locally before deployment.

D Use a single monolithic contract file for all services to simplify management.

💡 Hint

Think about automation and centralization for large-scale coordination.

A Pact Broker centralizes contracts and automates verification, making it scalable and manageable for many services.

❓ tradeoff

advanced

Tradeoffs of Using Contract Testing vs. End-to-End Testing

Which statement best describes a tradeoff when choosing Pact contract testing over full end-to-end testing?

A Contract testing provides faster feedback and isolates integration issues but may miss UI or infrastructure problems caught by end-to-end tests.

B Contract testing is slower and more expensive than end-to-end testing but provides better UI coverage.

C Contract testing replaces the need for any other testing types, including unit and integration tests.

D Contract testing requires deploying all services together, increasing complexity compared to end-to-end testing.

💡 Hint

Consider what contract testing focuses on versus what end-to-end testing covers.

Contract testing isolates API compatibility issues quickly but does not test full user flows or infrastructure, which end-to-end tests cover.

❓ estimation

expert

Estimating Pact Contract Test Execution Time in CI Pipeline

You have 20 microservices, each with 5 consumers. Each Pact verification test takes 10 seconds. Assuming all tests run sequentially, estimate the total Pact verification time in the CI pipeline.

A 1000 seconds

B 6000 seconds

C 1500 seconds

D 3000 seconds

💡 Hint

Calculate total tests as number of microservices × consumers, then multiply by test time.

Total tests = 20 services × 5 consumers = 100 tests. Each test takes 10 seconds, so total time = 100 × 10 = 1000 seconds.