On Mon, Jan 5, 2015 at 8:26 PM, Herwig Hochleitner <[email protected]>
wrote:
> (deftest foo
> (async done ..)
> (async done ..))
>
> Should this be the user's responsibility?
Sure preventing this would be nice. Each test only needs a single async
block.
> By the same logic, IAsyncTest instances aren't easily composable. Should
> there be explicit primitives for doing so (one serial, one parallel)?
> OTOH, if deftest with only one async child is the only "valid" idiom,
should
> it be encouraged by a (defasynctest foo done ...) form?
I don't really see the composition problem, tests run one after the other -
the runner can handle both kinds of tests.
I don't see what the purpose of serial or parallel is nor defasynctest.
(deftest foo
(async done
(go
(is (= x (<! c0))
(is (= y (<! c1))
(done))))
Or whatever.
--
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.
