Comments by "" (@bryanfinster7978) on "Contract Testing For Microservices IS A MUST" video.

Those should be implemented by the provider with whatever their xUnit framework is as separate behavior tests.
6
I've found Pact to be useful for services owned by a single team or closely related teams, but it becomes difficult if the teams are not working very closely together because Pact will break the provider's build as soon as the consumer asks for a change. Pact even suggested avoiding that use case. Awesome find on Specmatic. I've not come across that one yet. Adding it to the toolkit.
6
Not JUST as easily. Having something that can auto-test based on the OpenaAPI spec is pretty useful. I've used other similar tools to avoid hand-coding contract tests. You're right that you don't need a tool like this to do contract tests, it's just a toil reducer.
3
Strangely, some FE developers seem to think there's a difference between how we should treat UI and services. It baffles me. The only difference is the API. Services provide a machine-readable API. UI's provide a wetware-readable API. Otherwise, we should treat them the same.
2
@peterolson7351 Send them some Kent C. Dodds posts. :D
2
ONly if you wish to invest inordinate amounts of money developing a test you cannot trust. It doesn't matter how the customer sees it. You don't assemble a car before testing the components, and you don't test an assembled car in a way that will tell you if every component is working correctly. QA teams are a quality anti-pattern. See "Accelerate" by Forsgre, Humble, and Kim.
1
@RaMz00z Ties every change to the slowest change. :(
1