Programming

13362 readers

2 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago

MODERATORS

alyaza@beehaw.org

Hexorg@beehaw.org

remington@beehaw.org

Pact testing vs end-to-end testing (vlemmy.net)

submitted 1 year ago by show_me_the_clamps@vlemmy.net to c/programming@beehaw.org

7 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] ZeroEcks@lemmy.blahaj.zone 4 points 1 year ago

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