Hello, quick question about monolith contract test...
# general
h
Hello, quick question about monolith contract testing pipeline strategies: so we have monolith app (provider) with multiple consumers, what is the best strategy for blocking release(we do continues delivery) from provider? monolith(provider) got lots of responsibilities and all of subsystems are dependent on monolith, so when 1 consumer contract fail, should we block entire monolith release? until fix the contract? I know it is sounds same as monolith / micro services release issues, but I am looking for some similar real example for specifically contract testing, thanks
b
I mean, if it's going to break stuff, you should probably block the entire release, right? Otherwise you're deploying breakages.
Strategies to mitigate that somewhat extreme stance might include feature flags, versioned APIs, etc
The perspective should probably be that Pact (or any kind of testing) is just highlighting existing problems that weren't being caught before. Dealing with those problems isn't the job of the testing tools, it's more based around culture, practices, discipline, communication, etc 😇
h
I agree 100% Boris, yeap we are about to expand the contract testing, but little concerned that if we make soft fail(current one) the contract step, no one really care about lol ok I will throw some rocks to the organisation 🙂 thanks
💪 1
b
Good luck! I hope you can get traction with a simple reasoning approach 🙏
🥰 1