aphyr/prism

Automatically re-run clojure tests

Prism

Running tests with lein test means waiting for the JVM startup, and waiting for the project to compile. Prism recompiles and reloads files as you change them, and re-runs their corresponding tests immediately. Inspired by Midje's excellent autotest.

Usage

Check out Clojars for the latest version number, then add Prism to ~/.lein/profiles.clj:

{:user
 {:plugins [[com.aphyr/prism "0.1.1"]]
  :dependencies [[com.aphyr/prism "0.1.1"]]}}

You could alternatively add Prism to the dev dependencies in a given project--but this lets you use Prism against any project regardless of its project.clj.

Then, just run lein prism in your project directory. It'll do a full test first, then as you write .clj files, it'll re-run the corresponding test namespace. Prism assumes your tests are named foo.core-test.

Brought to you by

Raynes and Aphyr!

Why "Prism"?

It may be snooping on everything you write, and checking to make sure it's not dangerous. Or maybe not! Exciting!

License

Released under the Eclipse Public License; the same as Clojure.

prism's Issues

Run tests when file under resources is changed

I am working on a small parser using instaparse. I store the parser grammar under the resources directory. Whenever I change the grammar (which is referenced from a source file) I would like the tests to be re-run. I would not mind if this results in a full test as it may be difficult to figure out which source file depends on a resource file.

In general I think that prism should rerun tests whenever a file under the classpath is changed.

Run prism under test leiningen profile

I'm wondering if it would be possible to run prism under the test profile like a regular lein test run.

What I noticed is that when you start prism, it will make a normal full lein test run under the test profile. After that is done, it appears to spin up a new instance of the app (a Ring app in my case) under a different profile than test, possibly dev, which in my specific situation leads to several undesirable side-effects. In my case, there's much more logging under dev, and nrepl starts, whereas under the test profile all of these options are disabled.

I think that if under regular lein test you can make the assumption that the test profile will be used, it would be also reasonable to expect auto-test plugins to also leverage the same leiningen profile.

Perhaps I'm doing this wrong and would love to know what your thoughts are on this.

Consider merging with quickie and lein-test-refresh

Prism exits if the first test run has a failing test, it should keep running.

Repro:

lein new example && cd example && lein prism