Add the ability to run a testNg/testStreaming test on its own #5338
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.
Motivation:
Currently,
testNg
is run aftershadedTest
is run when thecheck
command is invoked.However, even if there are updates to the source code,
testNg
won't attempt to recompile the source code.This can be easily reproduced by modifying a testNg class, and trying to run
./gradlew testNg
.This is because
testNg
currently depends on the classpath ofshadedTest
. As long asshadedTest
isn't invoked, theshadedTest.classpath
won't be updated.Modifications:
copyShadedTestClasses
declares the test classpath as an input, it is safe to rely oncopyShadedTestClasses
(just likeshadedTest
does). ModifiedtestNg
,testStreaming
to depend oncopyShadedTestClasses
instead.finalizedBy
dependency since it doesn't make sense to have a dependency betweenshadedTest
andtestNg
/testStreaming
.Result:
./gradlew testNg
and receive results correctly