I looked directly at the JUnit5 docs and found what I wanted: JUnit 5 User Guide › 2.8.6. That said, I didn't find that article very helpful, and their examples were writing JS (yes: JS in a Java test using Nashorn) in a string which seemed like a shit way of doing things to me, and I 'knew' there must be a better way. Some quick googling landed me on the ever-helpful Baeldung site, with JUnit 5 Conditional Test Execution with Annotations › 6.2.

I have previously looked at conditionalising tests in both Kotest (' Kotlin / Gradle / Kotest random exploration'), and then JUnit (' Kotlin: looking at JUnit instead of Kotest'), but in the case of the JUnit ones, they were all 'canned' conditions, eg: In this case, I need to base the conditionality on my own logic. And that's legit, so I needed to be able to conditionalise (is that a word? Is now I guess) those tests based on whether the web service is up. I slapped my forehead on this because obviously they would fail because I don't have that web service running ATM.

This in itself is OK as I am half-way through doing something, but the tsts that were failing were the ones for a different article: ' Kotlin / TDD: writing the tests for a small web service'. To my dismay I saw a bunch of failing tests. I sat down to continue my 'next' blog article, which will be about delegated properties in Kotlin (will cross link here once it's done), and as a first step I ran my tests to remind myself where I got to.

Kotlin junit 5