>Currently we have two ways of running/skipping a slow test You wanted to say "at least two", did you? There are properties like calcite.test.druid which target a single test class.
>Does this make sense considering the ongoing work of moving to Gradle and JUnit5? The current Gradle-JUnit5 build uses **both** skipping options at the same time, because I want minimal changes to the source code. I'm not sure what is the better way, but I do like how JUnit5 enables to have short tags and tag expressions to filter tests. We could even tag tests with "@ExpectedDuration" and provide an option like "run all tests that typically fit in 5sec" >to unify the two by annotating all slow tests with the appropriate annotation I would suggest doing that after Gradle migration. WDYT? Vladimir
