you can also move to the failed test and press C-c ' and it will show
them in the mini-buffer
On Tue, Dec 21, 2010 at 11:47 PM, Michael Ossareh ossa...@gmail.com wrote:
On Tue, Dec 21, 2010 at 21:36, Michael Ossareh ossa...@gmail.com wrote:
On Tue, Dec 21, 2010 at 16:16, Phil Hagelberg
On Dec 21, 7:16 pm, Phil Hagelberg p...@hagelb.org wrote:
If you're already using swank then you can try clojure-test-mode; it
clears out all deftests in between test runs.
https://github.com/technomancy/clojure-mode/blob/master/clojure-test-...
It also highlights failures in the test buffer
On Dec 22, 8:54 am, Constantine Vetoshev gepar...@gmail.com wrote:
clojure-test-mode is pretty nice, but is there any way to make its
test namespace naming convention configurable?
It currently expects src/com/company/project/file.clj to correspond to
test/com/company/project/test/file.clj. I
Hi everyone,
My typical development workflow is to use leiningen to create a
project stub, modify project.clj to add swank-clojure as a dev-
dependency, and run lein-swank and connect from Emacs slime. As I
create and modify files in the test and src namespaces/directory
structures, I use C-c
You can delete the entire test namespace with `remove-ns` and then do
`(require ... :reload)`.
Or try Lazytest. :)
-Stuart Sierra
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that
On Dec 21, 10:35 am, Alyssa Kwan alyssa.c.k...@gmail.com wrote:
What about when I need to delete a unit test? Reloading the test
buffer doesn't remove it, and I need to either restart swank or
reconnect slime, or manually remove those tests using (unmap-ns).
Surely there's a better way...
If
Awesome!!! This absolutely does the trick!
On Dec 21, 7:16 pm, Phil Hagelberg p...@hagelb.org wrote:
On Dec 21, 10:35 am, Alyssa Kwan alyssa.c.k...@gmail.com wrote:
What about when I need to delete a unit test? Reloading the test
buffer doesn't remove it, and I need to either restart
On Tue, Dec 21, 2010 at 16:16, Phil Hagelberg p...@hagelb.org wrote:
It also highlights failures in the test buffer for better feedback.
when there is a failure where are the details of the failure printed out to?
I love that the highlight shows me which test have errors, but since I've
moved
On Tue, Dec 21, 2010 at 21:36, Michael Ossareh ossa...@gmail.com wrote:
On Tue, Dec 21, 2010 at 16:16, Phil Hagelberg p...@hagelb.org wrote:
It also highlights failures in the test buffer for better feedback.
when there is a failure where are the details of the failure printed out
to? I
