🔗 Microservices & Contract Testing
Practice the full contract testing workflow — from reviewing OpenAPI contracts and identifying schema gaps, to writing consumer-driven Pact tests, verifying providers, classifying breaking changes, and planning integration testing across dependent services. Pairs well with the API Automation practice area and the adding contract tests with Pact guide.
Pact · Contract testing
// Practical Assignments(5)
API Contract Review
Review an OpenAPI 3.0 contract for a user-profile microservice before implementation begins — identify schema gaps, undocumented error responses, ambiguous field definitions, and missing acceptance criteria, then produce a test-idea catalogue.
Pact Consumer Contract
Design and document consumer-driven contract tests for the ShopFlow Orders service — specifying the minimum interactions it needs from the User Profile provider, writing Pact-style interactions with provider states and type matchers, and explaining the CDC workflow.
Provider Verification
Verify that the User Profile service satisfies two consumer contracts — plan provider states, run verification against a failing contract, diagnose the root causes, and recommend fixes and a CI integration strategy.
Backward Compatibility Testing
Classify eight proposed User Profile API changes as breaking or non-breaking, identify affected consumers, assign risk ratings, generate regression test ideas, and recommend a versioning and release strategy.
Microservice Integration Test Plan
Plan integration testing across three ShopFlow microservices for the v2.3 release — map service dependencies, define critical workflows, scope the test effort, design mock/stub strategies, and document environment, test data, failure scenario, and observability needs.