Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
33 results for “Contract Testing”
Contract Testing
Verifying that a provider satisfies the expectations each of its consumers actually relies on, without running all the services together.
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
Load Testing
Driving a system with realistic traffic at a target volume to verify it meets its performance targets before real users do.
Abstraction
Exposing what a component does while hiding how it does it, so callers depend on the contract rather than the mechanism.
Booking.com's Experimentation Platform
Booking.com runs over a thousand concurrent experiments and treats the ability to test any change safely as a platform capability rather than a product feature.
Chaos Engineering
Deliberately injecting failure into a system to discover, before an incident does, which of your resilience assumptions are false.
Fitness Function
An automated check that an architectural characteristic still holds, run continuously rather than reviewed occasionally.
Game Day
A scheduled exercise in which a failure is deliberately introduced and the team responds as though it were real, to test the system and the response together.
LLM Evaluation
A repeatable measurement of whether an AI system's outputs are good enough, on cases that reflect the actual task.
Quality Attribute Scenario
A structured, testable statement of a non-functional requirement: source, stimulus, environment, artefact, response, response measure.
Restore Drill
A scheduled, timed exercise of restoring from backup into a clean environment — the only thing that converts a backup from a hope into a control.
Semantic Diffing of API Schemas
Comparing the published contract between builds and failing the build on a breaking change, so compatibility is mechanical rather than remembered.
Test Pyramid
A distribution of tests weighted towards many fast unit tests, fewer integration tests, and very few slow end-to-end tests.
Zero-Downtime Migration
Changing a schema or system while it stays in service, by adding the new alongside the old, migrating, then removing the old.
gRPC
A contract-first RPC framework using Protocol Buffers over HTTP/2, with generated clients and servers and first-class streaming.
A serverless API works in testing and fails under load with connection errors. The database is at 5% CPU. Explain and fix.
The mechanism Serverless functions scale by creating independent execution environments , each with its own process and its own connection pool. Two hundred con
Peak trading day is six weeks away and expected to be four times normal traffic. What do you do in those six weeks?
What the interviewer is testing Whether you can run a readiness programme rather than just "add servers", and whether you know what fails at peak that does not
TSB's 2018 core banking migration moved 1.9 million customers in a single weekend and failed publicly. What would you have required before approving that cutover?
The case, as publicly reported In April 2018 TSB migrated from a platform rented from Lloyds Banking Group to Proteo4UK, built by its parent Banco Sabadell. The
You need to ship a rewrite of the pricing engine. Same inputs, same expected outputs, completely new implementation. How do you release it?
What the interviewer is testing Whether you know that release strategy is part of architecture, and whether you reach for verification techniques beyond "test i
Your system handles 1,000 requests per second today. Marketing says a campaign will bring 10,000 next month. What breaks first, and how do you find out?
What the interviewer is testing Whether you reason about bottlenecks systematically or start adding servers. The shape of the answer Scaling is not uniform. Som
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
Testing Strategies
The pyramid, and the contract tests distributed systems add to it.
Contract Tests
Capturing what consumers actually use, not what the API documents.
DR Testing
Restore drills, timed against the stated RTO, into a clean environment.
Load Testing
Realistic data, realistic mix, and a ramp rather than a step.
Resilience Testing
Exercising retries, breakers and fallbacks that are otherwise never run.
Soak Testing
Long runs that surface leaks and slow degradation.
Stress Testing
Pushing past target to learn what breaks first and how it fails.
API Documentation
OpenAPI as a machine-checked contract rather than as prose.
Abstraction & Encapsulation
Hiding mechanism behind contract, and protecting invariants by owning state.
Game Days
Testing the response — runbooks, access, comms — not only the system.
Zero-Downtime Migration
Expand, migrate, contract — and the contract phase that never happens.
gRPC APIs
Contract-first RPC, generated clients and protobuf compatibility rules.