Hi all, Wanted to check one scenario. Let's say w...
# pactflow
p
Hi all, Wanted to check one scenario. Let's say we have a consumer and a provider. Now provider sends this payload
Copy code
{
"A": "XYZ1",
"B": "XYZ2",
"C": "XYZ3",
}
The consumer however consumes only this :
Copy code
{
  "A": "XYZ1",
  "B": "XYZ2"
}
The pact still passes as consumer's needs are met. (It got A and B) In my project. Both team were initially using A and B in their payload. A new element C needs to be added. I am from the provider side. When I add element C in the provider side, tests still pass. And the CONTRACT on pact-broker is not showing the updated contract (with C element). This has created a dependency for consumer to complete its implementation for Provider side story to be marked "COMPLETED" (after adding green test cases). Can this be avoided? Or is this the intended behavior?
m
This has created a dependency for consumer to complete its implementation for Provider side story to be marked “COMPLETED” (after adding green test cases).
why does the provider side story include waiting for the consumer contract to be updated?
This has created a dependency for consumer to complete its implementation for Provider side story to be marked “COMPLETED” (after adding green test cases).
Can this be avoided? Or is this the intended behavior?
this is the intended behaviour. Consider that some consumers may not need the additional field, by forcing it into the contract now you don’t know what consumers actually use/need from the provider
💯 1
☝️ 1