Fix the InvocationTargetException when running tests with Gradle #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
sainaen
force-pushed
the
fix-gradle-invocation-ex
branch
2 times, most recently
from
f1517ee
to
4d124cd
Compare
Static inner class ExpectedMatch was annotated with @org.junit.Ignore. Since it's not a test, using @ignore breaks assumptions of the JUnit4Runner when Gradle tries to enumerate ignored tests.
sainaen
force-pushed
the
fix-gradle-invocation-ex
branch
from
4d124cd
to
17b499e
Compare
|
Thanks too! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Static inner class ExpectedMatch was annotated with @org.junit.Ignore.
This broke assumptions of the JUnit4Runner expecting to find a test class
when Gradle tries to enumerate ignored tests. Making it
privateinstead of ignoringsolves the problem.
For example, here's the exception in the latest (passing) build: build 95.