-
-
Notifications
You must be signed in to change notification settings - Fork 481
Unable to discern reason for junit provider test failure #370
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
Comments
Thanks for all the information, I was able to reproduce it with a local project. |
Found the issue. {
"accessTokenValiditySeconds": 0,
"allowedScopes": [
],
"autoApprove": false,
"clientSecret": null,
"grantTypes": [
],
"id": "29b16b57-8212-4aeb-a180-b021399c0012",
"privileges": [
],
"redirectUris": [
],
"refreshTokenValiditySeconds": 0,
"secretRequired": false
} If the name is optional, you can leave it out of the consumer test. |
So it sounds like it's an issue in how the error diff is displayed? |
Yes, I think the output is really hard to see what was wrong and needs to be improved. |
Improved it a bit by showing more localised diffs for missing elements:
|
Conflicts: pact-jvm-matchers/build.gradle
pact-jvm = 3.3.1
pact-spec-version = 3.0.0
initial SO post
unable to debug as failures only happen on jenkins
Test logs:
relevant interaction:
generating fragment:
The text was updated successfully, but these errors were encountered: