Juho Teperi

Yes, bat-test code is more complex as it uses lower level c.t.n. functions so it can only run tests in the changed namespaces. `reload-and-test` logic is similar to `repl/refresh`.

I'm using following function in boot-alt-test to combine collection of reporters, should we add this to `eftest.report`? ```clj (defn combined-reporter "Combines the reporters by running first one directly, and others...

Another example here: https://github.com/metosin/bat-test/blob/master/src/metosin/bat_test/cloverage.clj The difference between this and circleci.test is that, With circleci.test one runs `cloverage` lein plugin which then calls into circleci.test to run the tests while Cloverage...

Missing ex-data is probably because Boot/Bat-test running eftest inside a pod. No easy solution, because exceptions can't be thrown from pod back to boot main context, boot-cljs does some magic...

I'd guess this was caused by upgrading org.apache.maven.wagon/wagon-http: https://github.com/boot-clj/boot/commit/55e4b552f475b6ef434a523a6a3580cfcfd603e9#diff-9db74cbad6290729409297ab0f2a33a6R21 I don't see why Pomegranate wouldn't work with the latest Wagon-http but that does seem like the obvious reason. I think...

Not really. But I would avoid anything which prevents using `:keys` destructuring, like namespace qualified keywords.

I don't see myself using other than hiccup. Instead of making `render` a monolithic task rendering with many different engines, maybe a separate task should be done for each template...

The things which bothers me is that if we are going to include some template engines we also need to add dependencies for them. I would like the dependencies were...

What Boot version are you using?

`test` scope can be used to exclude dependencies from `uber` task or from being transitive dependencies of a created package: https://github.com/Deraen/saapas/blob/master/build.boot#L36