gradle: how to run tests of all projects?

[Kevin Rushforth]

I see. In that case, the following will run follow-on tests:

gradlew --continue test

That's what I usually do for a full test run.

-- Kevin


On 10/8/2020 7:42 AM, Jeanette Winzenburg wrote:
>
> thanks for the quick answer :)
>
> Sounds like I wasn't clear enough, though (did mean unit tests): what 
> I'm puzzled about is that the unit tests of a dependent project (f.i. 
> controls) is _not_ run if the base has test failures.
>
> -- Jeanette
>
> Zitat von Kevin Rushforth <kevin.rushforth at oracle.com>:
>
>> "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
>>>
>
>
>