I really liked the article, thanks for writing.
I’m currently in a situation where I’m testing how a dotnet api interacts with a database.
Because our team is working with a nearly 40 year old database, we have an analyst who gives us sql queries that we then parameterize and execute from our api.
Also, no one on the team has any form of write/change access to this database.
Our team is practicing Tdd, which i’m proud of, and as a long time practitioner of tdd, I feel most of our tests are pretty good.
But there is still a decent amount of programming that happens in the sql queries, and in database triggers that were installed years and years ago (before our project even existed).
So, we’re integration testing the endpoints and services that interact with our problematic db.
I found your article insightful, but am curious how you’d test these software elements. We already use contracts, but I don’t know if that helps in this scenario… but what is collaboration testing?
Is that what we’re already doing?
Thanks again, really been enjoying your articles and videos