-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
JUnit: Error message in case of failed broker connection could be improved #1225
Comments
I had a look into this. Not really sure how to fix it. My impression is that it might even be intended like this because there are a lot of places where empty lists are returned in case an exception is thrown. Basically what happens is
Any ideas how to improve the behavior in this particular error case without breaking anything else? |
The fix is not to drop the cause exception, I'll make an update for that. |
4.1.9 released with the fix |
Hi, I have a similar issue. Scenario: Can you please provide any help with this issue? I have tried adding the pact broker SSL cer to JVM, but it still doesn't work. Thanks a lot |
@YingzheHeBetty can you open a separate issue for that. This issue is about the error message, not fixing the cause of the error. |
Scenario:
au.com.dius.pact.provider.junitsupport.loader.NoPactsFoundException: No Pact files were found to verify
It would be much more helpful if the error message contains the reason instead of having to scroll through logs (especially because sometimes WARN gets disabled for tests and the WARN message might not be shown at all)
Not sure if this is somehow related to #1092
The text was updated successfully, but these errors were encountered: