Bump to JUnit 5.11 M1, add FieldSource tests & rely on JUnit Platform for test method discovery

[mannodermaus]

No description provided.

[bddckr]

Instead of this hardcoded list, should the finder look for symbols annotated with @Testable (or another annotation that is itself annotated @Testable instead? See the Jupiter docs:

In order to facilitate test discovery within IDEs and tools prior to launching the JUnit Platform, TestEngine implementations are encouraged to make use of the @Testable annotation. For example, the @Test and @TestFactory annotations in JUnit Jupiter are meta-annotated with @testable. Consult the Javadoc for @Testable for further details.

https://junit.org/junit5/docs/current/user-guide/#test-engines-custom

This should help to support other test frameworks' TestEngines.

[mannodermaus]

The idea behind this declaration is to allow introspection of Jupiter's annotations by name, even for devices that don't support Java 8 yet. If we look inside of these annotations too much, we risk crashing because of unsupported features (e.g. when detecting @Repeatable in the meta-annotations). I do like the idea of opening up the scope beyond just Jupiter for devices that do support JUnit 5, though, so I cleaned it up a little in the latest commits. Now the annotations are only looked up for old devices and the newer ones only use what the discovery process of the platform returns to it, removing redundancy. ✨

That being said, most of the engines I was able to test require APIs that aren't available on Android (Spek, Cucumber). But hey: At least our Android bridge tried to load them in the first place - I call that a first step win. 🤷‍♂️

[bddckr]

Thanks for the explanation! That all makes sense to me!