In contrast to mvn test, ./gradlew test appears to also work JUnit Quickcheck test suites and executes them.
Known Issue
The increased coverage added with #28 reveals an issue related to hash collision handling of SetMultimap, see test output below:
> Task :test
io.usethesource.capsule.SetMultimapPropertiesTestSuite$PersistentTrieSetMultimapTest > sizeAfterInsertKeyValues FAILED
java.lang.AssertionError at Assert.java:89
Caused by: java.lang.AssertionError at Assert.java:89
io.usethesource.capsule.SetMultimapPropertiesTestSuite$PersistentBidirectionalTrieSetMultimapTest > sizeAfterInsertKeyValues FAILED
java.lang.AssertionError at PropertyVerifier.java:114
Caused by: java.lang.UnsupportedOperationException at PersistentTrieSetMultimap.java:2141
io.usethesource.capsule.SetMultimapPropertiesTestSuite$PersistentTrieSetMultimapTest > sizeAfterTransientInsertKeyValues FAILED
java.lang.AssertionError at PropertyVerifier.java:114
Caused by: java.lang.UnsupportedOperationException at PersistentTrieSetMultimap.java:2141
128 tests completed, 3 failed
Running the tests with the added ignoreKnownFailures flag (i.e., ./gradlew test -PignoreKnownFailures) would exclude the failing tests. A proper fix for the underlying issue will be seeded in a subsequent PR.
Follow-up Action Items
investigate obtaining parity between the Gradle and the Maven builds (e.g., license check plugin, release plugin / process)
switch fully to Gradle build and remove Maven build
The PR covers:
build.gradle.kts
)Automatic-Module-Name
manifest attributeIn contrast to
mvn test
,./gradlew test
appears to also work JUnit Quickcheck test suites and executes them.Known Issue
The increased coverage added with #28 reveals an issue related to hash collision handling of
SetMultimap
, see test output below:Running the tests with the added
ignoreKnownFailures
flag (i.e.,./gradlew test -PignoreKnownFailures
) would exclude the failing tests. A proper fix for the underlying issue will be seeded in a subsequent PR.Follow-up Action Items