gradle: how to run tests of all projects?

[Kevin Rushforth]

I just tested it and it works fine for me. Are you sure the reason it 
didn't run the tests in the other projects (graphics, etc) was because 
they had been run successfully earlier and thus the tests were 
"up-to-date"? If you want to force the tests to rerun even if nothing 
has changed, you need to also specify the "cleanTest" target:

gradle --continue cleanTest test -x :web:test

-- Kevin

On 10/8/2020 8:29 AM, Jeanette Winzenburg wrote:
>
> ahh .. yeah, that's working, thanks :) Except that now it continues 
> with web testing as first, and I don't know how to exclude that, 
> something like
>
>     gradlew --continue test -x :web:test
>
> just stops again after the base failure ..
>
> But don't bother - it's the end of the working day and I need some 
> rest, will try again tomorrow (or simply run them one-by-one)
>
> -- Thanks again, Jeanette
>
>
>
> Zitat von Kevin Rushforth <kevin.rushforth at oracle.com>:
>
>> 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
>>>>>
>>>
>>>
>>>
>
>
>