Following the diagram from the rspec book https://www.google.com/search?safe=off&biw=1920&bih=978&tbm=isch&sa=1&ei=PAc3XIS9CdKlwQKFsZv4BQ&q=bdd+diagram+rspec&oq=bdd+diagram+rspec&gs_l=img.3...2551.2551..2981...0.0..0.54.54.1......1....1..gws-wiz-img.sniyBzxTc_0#imgrc=aLTVEu_1wuuRuM:

Midje has autotest, but this isn't smart enough to help you focus on what's important (when failing unit tests first, than integration tests etc) and runs unnecessary checks again and also misses other checks

In case you appreciate my input... I've done bdd (as in Rspec, capybara) for some 5 years but always "by hand" (or by intuition), without any strict process. I think (and have seen others say too) that writing the tests strictly first before the code is a tool - a learning tool. Past the learning phase it shouldn't be that necessary Which is why the tool might not exist for clj 🙂

Thanks for your response. I think the by hand BDD is too cumbersome (i've been there too), but when automated it could be a game changer I believe

I'm working on something like that at the moment. I felt obliged to ask if someone isn't working on it already

I see. Yeah it could be nice as well, best wishes!

Thanks! Maybe the BDD part of my question was confusing. I'm looking for smart test runners that help you stay in a flow