-
Notifications
You must be signed in to change notification settings - Fork 234
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
Producer tests failing with non-beta package #530
Comments
We are having the same issue. The below sample works for beta2 but not in 5.0.0 namespace Tests.Pact; public class SimpleEventProviderPactTest : IDisposable
}` |
Thanks for the really detailed bug report 🤘 |
@mefellows I've not looked into this yet but just tagging for visibility because it looks like it could be an FFI issue |
i saw the same, you need to set the http url for the message proxy server that pact-net spins up. you shouldn’t need to in the consumer facing dsl but this is a workaround |
Previous issues
I have searched issues in this and other pact-foundation repos, as well as searching online and attempting to sign up for slack.
Version information:
Describe the bug
Producer tests which previously worked using 5.0.0-beta.2 fail to run when updated to 5.0.0. Tests fail with
Steps To Reproduce
Update PactNet from 5.0.0-beta.2 to 5.0.0
Running tests using several test runners and xunit.
Example test
Expected behavior
Tests should run and pass or fail based on contract using latest non-beta package.
Log Output
Additional context
Comparing this to the run which works successfully using beta.2 it appears to be attempting to connect to message://localhost:49152/pact-messages rather than http://localhost:49152/pact-messages/. This appears to be where it fails.
pact_verifier::provider_client: Sending request to provider at message://localhost:49152/pact-messages/
vs
pact_verifier::provider_client: Sending request to provider at http://localhost:49152/pact-messages/
Looking at the changes between beta.2 and 5.0.0 the main thing is the underlying ffi package, it does look like something may have changed with the ProviderInfo class in there.
5.0.0-beta.2...5.0.0
FFI_VERSION="0.4.16" > FFI_VERSION="0.4.23"
If this is the case I'm surprised we are the only people having this issue unless most are doing API verification.
The text was updated successfully, but these errors were encountered: