Easy API Simulation with Hoverfly JUnit Rule
specto.io
specto.io
Yes, interesting idea! I guess it does mean that there is a "testing contract" with the consumers? ie. the consumers need to know what example cases they can depend on in _their_ tests?
In terms of process there's a big difference with tools like Swagger though in that you have to create the tests and corresponding implementation before you can start integration testing consumers, which might be tricky if you have multiple teams working on new services. I guess this is only really a problem when you're starting out as the tests and implementation should be ready soon after.
If we just use this for testing I was also wondering if you would use this at the beginning of your project or would you add it when the test suite start slowing down?