A library-holds microservice ships to production without a coordinated release of catalog or fines neighbors. How should its automated tests be organized?
Select an answer to reveal the explanation.
Short Explanation
If a desk can open without waiting for every other city office, its tests should too. Confidence lives with the shippable unit, plus a thin contract check—not a whole-estate gate every time.
Full Explanation
Independently deployable microservices need independently runnable tests. Most confidence is earned inside the changed service, with a thin verification of the network contract it publishes. Forcing a full multi-service suite before every one-service ship couples release cadence back into a monolith through the test door.