kaocha

Official support channel: https://clojureverse.org/c/projects/kaocha
2020-11-18T15:21:35.083700Z

ok problem solved, the code is not publicly available but it's quite simple tbf

2020-11-18T15:30:03.084400Z

is there anything available to re-run automatically failed tests?

2020-11-18T15:31:01.085100Z

well actually it might be quite trivial to do if in the test report I know which one failed, and I use kaocha.repl to re-run them

dharrigan 2020-11-18T15:35:33.086400Z

I normally have a seperate term open

dharrigan 2020-11-18T15:35:36.086700Z

and I execute this

dharrigan 2020-11-18T15:35:40.086900Z

clj -M:test -m kaocha.runner --watch

dharrigan 2020-11-18T15:35:48.087200Z

that will reexecute all tests on any file save

2020-11-18T15:36:06.087700Z

ah that's cool but I need retry for CI, since some tests depend on external infra

2020-11-18T15:36:10.087900Z

that can fail sometimes

dharrigan 2020-11-18T15:36:33.088300Z

oh okay. that sounds a bit flakey - can't you mock out the external bits?

2020-11-18T15:36:53.088900Z

I guess it would not make sense for the type of tests to mock anything

dharrigan 2020-11-18T15:37:05.089600Z

it's like having static variables in your codebase with a heisenberg test failure

dharrigan 2020-11-18T15:37:13.089800Z

kk

dominicm 2020-11-18T21:27:01.091600Z

Those external bits might be directly impacted by the code changing, like triggering a waf accidentally... Just speculating. You're probably right that something like pingdom is a better tool for that though.