I have two projects, project A and Project B. Both are written in groovy and use gradle as their build system.
Project A requires project B. This holds for both the compile and test code.
How can I configure that the test classes of project A have access to the test classes of project B?
Advertisements. The test task automatically detects and executes all the unit tests in the test source set., Once the test execution is complete, it also generates a report. JUnit and TestNG are the supported APIs. The test task provides a Test.
Test execution. Gradle executes tests in a separate ('forked') JVM, isolated from the main build process. This prevents classpath pollution and excessive memory consumption for the build process. It also allows you to run the tests with different JVM arguments than the build is using.
You can expose the test classes via a 'tests' configuration and then define a testCompile dependency on that configuration.
I have this block for all java projects, which jars all test code:
task testJar(type: Jar, dependsOn: testClasses) { baseName = "test-${project.archivesBaseName}" from sourceSets.test.output } configurations { tests } artifacts { tests testJar }
Then when I have test code I want to access between projects I use
dependencies { testCompile project(path: ':aProject', configuration: 'tests') }
This is for Java; I'm assuming it should work for groovy as well.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With