I just tried out both lein-difftest and gui-diff and they work just great.
I'd love a `lein test` command that defaulted to the former and could
resort to the latter when things got hairy. But that's just wishful
thinking at the moment :)
Thanks you Sean for the advice as well - the workflow you
Sean Corfield seancorfi...@gmail.com writes:
You'll find your workflow greatly improved by using nrepl (or
slime/swank) and running tests directly from Emacs - and that applies
whether you're using bare clojure.test, midje or expectations.
For nrepl.el, via clojure-test-mode, There is an pull
First of all, I must say I'm new to testing in Clojure. My current workflow
is pretty simple:
* Edit + save the tests (which use clojure.test - I hear Midje is better
though) in emacs
* Run `lein test` in the terminal
* recur
But then the printed values (triggered when e.g. an `are` case
Hi Victor,
I've developed something I use on my own projects to compare pretty printed
test failure output. The final piece for it would be to incorporate its
test failure report diffing into a leiningen plugin that wrapped lein test.
https://github.com/AlexBaranosky/gui-diff
On Thu, Feb 14,
On Thu, Feb 14, 2013 at 3:06 PM, vemv v...@vemv.net wrote:
But then the printed values (triggered when e.g. an `are` case fails) are
fairly illegible, especially when big.
Can I get the test runner to pprint its output? Is my workflow improvable
anyway?
I use lein-difftest for this:
You'll find your workflow greatly improved by using nrepl (or
slime/swank) and running tests directly from Emacs - and that applies
whether you're using bare clojure.test, midje or expectations.
I use expectations for testing and expectations-mode in Emacs. I can
run an individual namespace's
