Mark,
There isn't much documentation yet as it's not significantly different from
clojure.test. The cljs.test namespace itself has a docstring with updated
information. That's the best resource for now. Community updates to the
wiki are welcome of course :)
David
On Fri, May 8, 2015 at 2:49 AM,
I can't find any documentation or examples for using the new cljs.test
namespace. Can someone point me in the right direction? Thanks.
--
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 G
I suppose so, just using an async block just seems cleaner and simpler to
me and you're not modifying a type you don't control - not a big deal in
tests but you never know.
David
On Mon, Jan 5, 2015 at 9:12 PM, James MacAulay wrote:
> On Monday, 5 January 2015 20:00:17 UTC-5, David Nolen wrote
On Monday, 5 January 2015 20:00:17 UTC-5, David Nolen wrote:
> That can't actually work since the go block doesn't receive the done
> fn to proceed to the next test.
I was thinking of something like:
(extend-type ManyToManyChannel
IAsyncTest
(-invoke [ch done]
(take! ch (fn [_] (done
On Mon, Jan 5, 2015 at 8:26 PM, Herwig Hochleitner
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 c
2015-01-05 20:30 GMT+01:00 David Nolen :
> Definitely plans to support async and happy to take a patch.
>
> Basically I would like sugar that looks like this:
>
> (deftest foo
> (async done
> ...))
>
> This desugars into:
>
> (deftest foo
>(reify
> IAsyncTest
> (-invoke [_ don
That can't actually work since the go block doesn't receive the done
fn to proceed to the next test.
David
On Mon, Jan 5, 2015 at 7:13 PM, James MacAulay wrote:
> On Monday, 5 January 2015 14:30:35 UTC-5, David Nolen wrote:
>> The test runners should check for satisfies? IAsyncTest do nothing i
On Monday, 5 January 2015 14:30:35 UTC-5, David Nolen wrote:
> The test runners should check for satisfies? IAsyncTest do nothing if
> that's the return value of the test. Invoking done will gather
> reporting information and invoke the next test.
Ooo nice idea, then we could just extend core.asy
Definitely plans to support async and happy to take a patch.
Basically I would like sugar that looks like this:
(deftest foo
(async done
...))
This desugars into:
(deftest foo
(reify
IAsyncTest
(-invoke [_ done]
...))
The test runners should check for satisfies? IAs
It's great to see unit test support in clojurescript. Are there plans to
support asynchronous tests or should I keep using cemerick's cljs.test for
this?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are sub
Got it. Thanks.
I voted for the jira issue.
On Tue, Dec 30, 2014 at 3:49 PM, David Nolen
wrote:
> This is a tooling issue more than anything, you need to recompile the
> namespace with the `run-tests` expression.
> However, there is utility to a :recompile-dependents flag, and we
> already hav
This is a tooling issue more than anything, you need to recompile the
namespace with the `run-tests` expression.
However, there is utility to a :recompile-dependents flag, and we
already have a JIRA ticket for this. When it is implemented it will
trigger all dependent namespaces to recompile.
Dav
I have played with the tutorial provided here:
http://keeds.github.io/clojurescript/2014/12/19/cljs-test.html
It seems that new tests inside an existing namespace are not run when using
lein cljsbuild auto test.
Is it a bug in cljs.test?
On Wednesday, 24 December 2014 20:40:03 UTC+2, David N
Time between releases are pretty variable though they tend to be
pretty frequent around new features like cljs.test as issues need to
be ironed out.
I'll probably cut another release on Friday.
David
On Wed, Dec 24, 2014 at 1:32 PM, Yehonathan Sharvit wrote:
> Great news David!
>
> What is the
Great news David!
What is the usual delay (in days) between commit to the master and release?
On Wednesday, 24 December 2014 20:18:39 UTC+2, David Nolen wrote:
> The `are` macro isn't in a current release, however it's in master and
> will appear in the next one. Otherwise Russell's assessment i
The `are` macro isn't in a current release, however it's in master and
will appear in the next one. Otherwise Russell's assessment is
correct.
David
On Wed, Dec 24, 2014 at 1:13 PM, Yehonathan Sharvit wrote:
> What about the 'are' macro?
>
>
>
> On Wed, Dec 24, 2014 at 7:38 PM, Russell Mull
> w
Yes, it's there. The things I listed are the only differences I could find.
The separation of macros makes it a little confusing, but it's pretty easy
to find in the source:
-
https://github.com/clojure/clojurescript/blob/master/src/cljs/cljs/test.cljs
-
https://github.com/clojure/clojurescript/
What about the 'are' macro?
On Wed, Dec 24, 2014 at 7:38 PM, Russell Mull
wrote:
> Things that aren't in cljs.test:
>- with-test
>- run-tests can take a custom environment parameter. Things that
>required rebinding a var in clj.test are configured with an entry in the
>environm
Things that aren't in cljs.test:
- with-test
- run-tests can take a custom environment parameter. Things that
required rebinding a var in clj.test are configured with an entry in the
environment.
- :reporter, instead of rebinding the report function
- :testing-contexts i
What is the gap between clojure.test and cljs.test?
For exmaple: is the `are` macro implemented in cljs.test?
On Wednesday, 17 December 2014 23:54:09 UTC+2, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com
Now that var is implemented. Could we expect the support of private functions
in cljs?
On Wednesday, 17 December 2014 23:54:09 UTC+2, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
I just cut 0.0-2498, the only change is support for
`cljs.test/use-fixtures` analogous to `clojure.test/use-fixtures`.
David
On Wed, Dec 17, 2014 at 4:54 PM, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com
Looks great, thanks so much!
I was happy to see the "TODO: support async" comment in test.clj, as I am
currently using Chas Emerick's clojurescript.test for very async-heavy stuff. I
ended up writing a macro which I think improves the ergonomics of portable
async testing quite a bit:
https://g
Does cljs.test support asynchronous tests? What are benefits of cljs.test over
clojurescript.test (https://github.com/cemerick/clojurescript.test)?
Clojurescript.test also a port of clojure.test but has additional API for
writing asynchronous tests.
On Wednesday, December 17, 2014 2:39:22 PM
really exciting stuff, thanks a lot
On Wednesday, December 17, 2014 3:54:09 PM UTC-6, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
> README and source code: https://github.com/clojure/clojurescript
>
> New release version: 0.0-2496
>
> Leiningen
25 matches
Mail list logo
