Zitat von Kevin Rushforth <kevin.rushfo...@oracle.com>:
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"?
hmm .. not entirely certain: here's the scenario
- working on those regression tests for ObservableList
- have tests in both base and controls the fail before the fix to the
old issue 8093144, all tests pass after the fix
- in ObservableListWrapper, I have a both versions (chosen by a static
toggle pre/fix)
- compile with fix
- run gradle --continue test -x :web:test
- all are passing
- toggle the switch to use the prefix implementation (now I expect
test failures in base and control)
- run the gradle cmd above
- testing stops after tests in base failed
So there were no code changes in controls and the tests formerly
passed - but the change in base should mark the control test as
requiring re-run or not?
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
yeah, that's working, thanks :)
That option is fine, so don't need understanding the upper part -- it
just itches <g>
-- 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.rushfo...@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.rushfo...@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
