Using e.g. Datomic's support for transient in-memory databases in tests, along with test.check's property-based testing and (I strongly suspect) the failure data added by tools like test.chuck's for-all macro produces a perfect storm with eftest. Unlike lein test or other tools (including Calva's REPL), if the output happens to contain a Datomic DB, it will print out all the data in that. Even for a transient DB, that's a staggering amount, thousands of lines.
Using e.g. Datomic's support for transient in-memory databases in tests, along with test.check's property-based testing and (I strongly suspect) the failure data added by tools like test.chuck's
for-all
macro produces a perfect storm with eftest. Unlikelein test
or other tools (including Calva's REPL), if the output happens to contain a Datomic DB, it will print out all the data in that. Even for a transient DB, that's a staggering amount, thousands of lines.Representative:
The output of
lein test :only sample-test/test-db-things
is something like this:The output of eftest for that is in the hundreds of kilobytes.
Calva solved a very similar problem without, I believe any Datomic-specific special-casing.