"gradlew test" is sufficient to run the headless tests (e.g., the ones
in base, graphics, controls, etc). To run the headful tests, there are
two additional gradle options:
-PFULL_TEST=true
-PUSE_ROBOT=true
The first enables headless tests (which are in the systemTests project).
The second additionally enables the Robot-based tests. The Robot tests
are likely to fail unless you make sure not to touch your system and
disable your screen saver (or set the timeout to long enough that it
doesn't start during the tests).
-- Kevin
On 10/8/2020 7:12 AM, Jeanette Winzenburg wrote:
With
./gradlew test
I expect that tests of all projects are run (and think I have seen
that expected behavior, but who knows ;), at least those projects with
changes that might effect the tests.
Since today (?), it looks like it stops after running base tests if
there's a failure in any of the base tests. Without that failure, it
moves on to controls tests.
Anything changed, or my expectation wrong, or anything else?
-- Jeanette
