search

slagyr / speclj

pronounced "speckle": a TDD/BDD framework for Clojure.
MIT License
459 stars 58 forks source link

Handle :optimization :none #100

Closed mike-thompson-day8 closed 9 years ago

mike-thompson-day8 commented 10 years ago

Currently specljs doesn't handle the cljsbuild option:optimizations :none.

You might be interested to see how I got it to work for com.cemerick/clojurescript.test because the principal would transfer fairly easily to specljs.

See this seed project - which contains a link to a gist for specljs.

BTW, as feedback: although we liked specljs, we can't use it because it doesn't handle async tests, which is a show stopper for us. We will have to go back to cemeric/clojurescript.test for the moment.

slagyr commented 10 years ago

Cool. We'll save this one for later.

What is it about speclj that makes you say it doesn't handle async tests?

mike-thompson-day8 commented 10 years ago

@slagyr I mean it doesn't allow for this kind of handling:
https://github.com/cemerick/clojurescript.test#asynchronous-testing

wilkerlucio commented 10 years ago

@slagyr I think the problem is that to handle async testing you have to provide a way to manually invoke the next test, because there is no way for the test framework to know about which point in time the test ended. This is very important for ClojureScript since a lot of JS apis are async only.

slagyr commented 9 years ago

118 addresses the async aspect.

As for :optimizations :none, it requires a new means of running the specs. The way I've done it is by creating a web page that'll run the specs, and invoking them with phantom. Auto running can be achieved this way too.

This is better addressed by the speclj-template project: https://github.com/ecmendenhall/specljs-template

Issue moved: https://github.com/ecmendenhall/specljs-template/issues/2