|
|
|
|
|
by BizyDev
1533 days ago
|
|
Didn't even knew that Spotify wrote an article about this "methodology" thanks for sharing. No, all you have to do is spin up your service under test, its database and the service bus/event hub/whatever you use to communicate between services. Nowadays with Docker it's really easy and fast to spin up test instances during your test run. (4-5 LoC with a good library in C#). Since 1 or 2 years I'm doing the exactly same thing on my projects and it works great to speed-up development process and if a bug pops in production it's really easy to add it as a future test case. You're only attached to the input request (endpoint, query params, request body) and the response body. But that's ok because it's already a part of the contract between the API and its consumers. That's it. |
|