Am 29.04.23 um 15:44 schrieb Vladimir Sitnikov:
Felix> That is what I thought, too. But even changing the source of the
test (with something, I know will break it), didn't work. Spock tests in
the same package (src/components) will run just fine.
It turns out that junit5 tests were not executed
Felix> That is what I thought, too. But even changing the source of the
test (with something, I know will break it), didn't work. Spock tests in
the same package (src/components) will run just fine.
It turns out that junit5 tests were not executed since there was no
junit-jupiter engine on the tes
Am 29.04.23 um 10:59 schrieb Vladimir Sitnikov:
I guess the reason is that execute tests several times. Gradle caches
test results.
In other words, if you execute the same tests with the same source,
then the build does not execute tests again.
However, if you modify test code and/or change depe
I guess the reason is that execute tests several times. Gradle caches
test results.
In other words, if you execute the same tests with the same source,
then the build does not execute tests again.
However, if you modify test code and/or change dependency, then tests
would be re-executed.
batchTest
Hi all,
I tried to rebase pr 723 to the current main trunk and it seems to me,
that most tests are not run anymore. Maybe I am doing something wrong.
I usually do
> ./gradlew test
inside the checked out directory and it runs a lot of tests for a few
minutes.
Now it is ready after 6s and i
