Ok, so I went through the builds, searching for the one, where the number of tests dropped. Turned out to be the one I added the groovy support.
Did a while of searching for a solution and it seems that following the tutorials and importing "groovy-all" imported an insane number of libraries. So I tried out reducing that to only the test-related ones, and the Junit5 tests came back. But we should think of a way to be able to detect that in the future. Cause we never know if someone adds a dependency and a lot of our tests silently just stop running without any complaint. Think I'll create a Jira for coming up with something ... done PLC4X-68 Chris Am 25.10.18, 00:41 schrieb "Christofer Dutz" <[email protected]>: Hi all, I just noticed something. A while ago I added a test in the S7 module, which tested all sorts of combinations of types. This test alone added more than 7000 tests to the test-suite. We could see that in the trend for tests on Jenkins. Today I noticed a huge drop in the number of executed tests and it currently seems as if Junit5 tests are no longer being executed correctly. I’ll investigate the issue, but I have to admit that my trust in Junit 5 is again beginning to sink dramatically. Chris
