At my company there has been a move away from our large e2e testing suite for various reasons:
flaky tests
long build times
significant burden for multiple teams to contribute
The use of pact is seemingly only covering some small portion of each integration point between applications as large, comprehensive pacts that cover the full API and values used are considered too costly or coupled.
I am conflicted that we are losing test coverage of business use cases because there aren’t necessarily any tests that are automatically running a use case end to end.
How do you deal with this in your workplace and what is your position on e2e vs pact testing.
I have never actually managed to get it integrated, but I have always pushed for contract testing that’s maintained by both sides of the contract. This has the benefit of being able to create compatibility matrixes between services at the very least
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@beehaw.org
All things programming and coding related. Subcommunity of Technology.
I have never actually managed to get it integrated, but I have always pushed for contract testing that’s maintained by both sides of the contract. This has the benefit of being able to create compatibility matrixes between services at the very least