New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versions after 1.60.0 do not produce message pacts with providerStates populated #43
Comments
Below is the logs that I could find but I want to highlight what I find as the relevant logs.
Complete Log
|
I created a fork of the pact-ruby-standalone-e2e-example repository and created two branches that show the difference between the last working version (1.60.0) and the latest version (1.74.0). Reproduction scenario:
You could also inspect the difference in the output looking at this diff: https://github.com/cwdt/pact-ruby-standalone-e2e-example/compare/message-1.60.0...cwdt:message-1.74.0?expand=1 |
This is a bug report of such beauty it makes me weep a little tear. Thank you! |
Ok, so technically v2 does not support message pact, and
If you update the php code to use this format, you should be hunky dory. I'm sorry that the code changed under your feet - I usually make sure everything is backwards compatible, even if it's not "to spec". |
Thanks! I'll take a stab at that. I am secretly pretty pleased on of the PHP tests caught the change! |
Closing as we've worked out the cause. |
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):I hope I can make a better example in this ticket.
Software versions
Expected behaviour
This was working with standalone version 1.54.4 and up to 1.60.0. It seems that 1.61.0 broke the functionality. In this case, when I run my consumer tests, 1.60.0 produces a Pact providerStates in the message object.
With this message pact, the provider correctly validates the state/pact.
Actual behaviour
In version 1.61.0 to 1.74.0, when running the message consumer produces the following pact w/o providerStates populated.
So something appears to have happened between 1.60.0 and 1.61.0. I confirmed this is still broken in 1.74.0
Steps to reproduce
You are going to hate this. I hope @cwdt might be able to help.
const VERSION = '1.54.4';
withconst VERSION = '1.74.0';
failing)
The text was updated successfully, but these errors were encountered: