Skip to content
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

fix: Don't publish incomplete verification results #1166 #1167

Merged
merged 1 commit into from
Jul 10, 2020

Conversation

tinexw
Copy link
Contributor

@tinexw tinexw commented Jul 9, 2020

Fixes #1166

What is the best way to test this? I would like to add tests similar to the JUnit 4 ones. But I don't know how.

@anto-ac
Copy link
Collaborator

anto-ac commented Jul 9, 2020

I’m not familiar with that area of the code to comment on the implementation, but it would be good to see some tests added, at least to reproduce/cover the fix.

@tinexw
Copy link
Contributor Author

tinexw commented Jul 9, 2020

I’m not familiar with that area of the code to comment on the implementation, but it would be good to see some tests added, at least to reproduce/cover the fix.

I can add the most basic test to ensure that respective methods are called. I just thought it would be better to also add a test on an integration test level.

@tinexw tinexw force-pushed the junit5-filtered-pacts-fix branch from a069194 to f5d01e5 Compare July 9, 2020 21:17
@tinexw tinexw force-pushed the junit5-filtered-pacts-fix branch from f5d01e5 to 0727ff4 Compare July 9, 2020 21:54
@tinexw
Copy link
Contributor Author

tinexw commented Jul 9, 2020

I added the simple test.

@uglyog uglyog merged commit 0727ff4 into pact-foundation:master Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Verification results are published even though not all interactions were verified
3 participants