Hi, I have a question that always troubles me from...
# generalw
Wei Huang
10/17/2023, 9:56 PMHi, I have a question that always troubles me from using pact.
1. Pact is a great tool for contract/integration test, which is usually at the border of the system.
2. Both parties (consumer/producer) of the test needs to include Pact in their test suite so that contract testing really takes effect.
3. However, since it’s at the border, it usually means they belong to two different teams. It’s hard to impact the other team to accept the contract test and implement it.
Is my understanding true? or do I miss something? Thanks
m
Matt (pactflow.io / pact-js / pact-go)
10/17/2023, 10:16 PM
Is the problem that they disagree with what you have in the contract, or just don’t want to participate in the testing altogether?
w
Wei Huang
10/17/2023, 10:46 PMthe latter. They always want end-to-end test
m
Matt (pactflow.io / pact-js / pact-go)
10/17/2023, 11:17 PM
so aside from all of the documentation, videos and blogs we have, no 😛
😂 1
Matt (pactflow.io / pact-js / pact-go)
10/17/2023, 11:17 PM
Matt (pactflow.io / pact-js / pact-go)
10/17/2023, 11:19 PM
Matt (pactflow.io / pact-js / pact-go)
10/17/2023, 11:21 PM
Ultimately, if they don’t have pain it’s hard to convince them if they’re aren’t having problems. You can either
1. Capitalise on the pain/cost/problems - “hey, so i can see you’re struggling. here’s a better way that will reduce the number of grey / lost hair”
2. Make an argument about ROI (reduce the time/cost of testing)
3. Make an argument from better test strategy
I’ve found (1) to be the most powerful, frankly. So I’d be looking for opportunities to say “hey, that problem/pain you have - it’s because of the way you’re testing”
dusty stick 1
w
Wei Huang
11/20/2023, 6:25 AMThanks Matt. There may be another bigger problem in the other team. They think it’s QA’s responsibility to test the system. So they don’t have pain doing e2e test.🤨
facepalm 1
nod hmm yes 1
m
Matt (pactflow.io / pact-js / pact-go)
11/20/2023, 6:33 AM
Thanks Matt. There may be another bigger problem in the other team. They think it’s QA’s responsibility to test the system. So they don’t have pain doing e2e test.find the person/people who pay them. The argument is (crudely, I hope you can extrapolate) “those people are spending time writing and maintaining tests that are more complex, expensive and painful. We can all test smarter, and they’ll be able to focus their energy on higher value tests”