...
Currently all of the Robot based tests are ing in systemTests, and must live in the test.robot package.
...
- the JUnit jars
- each of the dependent modules (graphics has base tests in its classpath)
The dependent modules tests test classes are rarely used, but do contain items like the stub toolkit, so must be included.
...
Any packages not mentioned in the module info cannot be used for a shim, because the JDK does not allow addExport of unreferenced packages. In these cases, you will have to get clever with your shims, placing the test visible one shim in a visible package, perhaps calling a second layer of shim in a hidden package.
...
Capturing our classpath
During the build gradle test task, an @argfile form of the test classpath is created for each of the modules. This can be used for reference or with manual command lines. An example of this file is: build/testing/classpath_graphics.txt.
...
In build.gradle, there is a toggle that can be used to create additional output on from GradleJUnitWorker showing the command lines used to launch tests. This currently affects
GradleJUnitWorker.java and the system Sandbox tests. Modify this line (temporarily), and run tests with the gradle -info option. (The -info option to gradle enabled enables it to pass through stdout/stderr from the worker process).
...
Overview
Content Tools
ThemeBuilder