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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#excludedGroups
Was that wrong usage of
excludedGroups
before this PR?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we want to run integration tests and unit tests (ending in
*ClientTest
) with thenative
profile. For this purpose, we tend to ignore any exclusions that take place in other maven-surefire-plugin configurations within the java-shared-config pom or other child poms: https://github.com/googleapis/java-shared-config/blob/ac44ba11d2da2f649670867c520f90253a8a41ff/pom.xml#L807, so that we can explicitly include these tests. However, with the use ofexcludedGroups
in java-spanner-jdbc, this overriding of the exclusions gets ignored, therefore causing no integration tests to run innative
mode. Changing this toexclude
fixes this issue.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems correct usage to skip the integration test marked with
@Category(ParallelIntegrationTest.class)
in this repository.@mpeddada1 With this change in this PR, does
mvn test
skip the tests marked with@Category(ParallelIntegrationTest.class)
, such asITJdbcSimpleStatementsTest
andITJdbcReadOnlyTest
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. Just ran
mvn test
with this change and can confirm that tests annotated with@Category(ParallelIntegrationTest.class)
are skipped. Only unit tests are executed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for confirmation.