4 ms·
> but other than that, you should trust the API contract As someone who's been working in corporate integration for the past 6 years.. Never trust a contract.
by Mandatum 7y ago
> but other than that, you should trust the API contract
As someone who's been working in corporate integration for the past 6 years..
Never trust a contract. Be in WSDL, OpenAPI spec, Word documents or otherwise. I've worked with large tech vendors, I've worked with finance, I've worked with large consultancies. The only people that seem to get it right, is the people you don't want to work with because it's soul-crushing - think HL7 et al.
- hhjinks 7y agoThe point is you can't write unit tests for broken API contracts, so either you trust that the contract is upheld, or you've got bigger problems on your hands.
- Mandatum 7y agoDo you mean integration tests? I don't think API contracts should be a part of a unit test. A unit test should be self-contained, unless of course there is a tight coupling to an API.. Which I would steer clear from. That's why I value integration tests over most thing. I can see immediately that something is broken at a high level, what business impacts it has and explain what systems are affected.