mm another thing that I noticed now, is that if the exception is thrown outside of an is, and before any isassertion

the test will report saying that there are no assertions

which I guess makes sense but is a bit confusing since the assertions are there, they are just never reached

these tests that are causing so much trouble are the selenium like tests, and when something fails it normally just times out and throws an exception

and the few assertions are just at the end

anyway I guess this problem is not really related to the retry plugin

Yeah for these kinds of tests it should be possible to disable that check, not sure if we already have an issue for that. See also the kaocha/v2 wish list, this is something that could be opt-in

ah yeah cool

btw I added some cli-options but they never show up in the help

(cli-config [opts]
    (conj opts
          [nil "--[no-]retry" "Retry tests"]
          [nil "--max-retries" "Number of times to retry the tests"
           :parse-fn #(Integer/parseInt %)]
          [nil "--retry-interval" "How many milliseconds to wait before retrying"
           :parse-fn #(Integer/parseInt %)]))

either with the plugin enabled globally or enabled with --plugin