I run "lein quickie" to run all the Clojure tests and "lein cljsbuild auto 
unit-tests" for all the ClojureScript tests.

I prefer this over running individual tests for the following reasons:
 - I use cljx so this is easier than running the same clj/cljs test separately
 - it prevents a *lot* of bad behaviour (slow tests, broken tests outside of 
working set and so on)

On Tuesday, 27 January 2015 10:42:15 UTC, Thomas Heller  wrote:
> Hello everyone,
> 
> I recently started working in adding support for testing in shadow-build. I 
> have my own testing workflow but wanted to ask how everyone else does it? 
> ClojureScript AND Clojure because I'd like them to be as close as possible.
> 
> My CLJ workflow is opening a REPL and use "Run test under Caret" and "Re-run 
> last test action" via Cursive (cider before that) until that works and then 
> continue with the next test. Occasionally running all tests.
> 
> For CLJS I basically have no tests but my goal is to get to the exact same 
> workflow as in CLJ. It might need some adjustments due to the nature of 
> browsers, also there are some parts that can be tested via node and wouldn't 
> need a browser.
> 
> So far I have the ability to execute all tests or watch files for changes and 
> then execute only those affected by the changed files. I identify a test by 
> looking at the :require of the ns form. If cljs.test is in there it is a 
> test. Currently that only works with node, although a phantomjs/slimerjs test 
> "runner" should be pretty simple. Do you guys do anything special in the html 
> file associated with those or just boilerplate?
> 
> Would appreciate some examples of other testing workflows.
> 
> Thanks,
> /thomas

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.

Reply via email to