This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-24
Channels
- # architecture (7)
- # beginners (73)
- # boot (4)
- # cider (48)
- # cljsjs (7)
- # cljsrn (27)
- # clojure (206)
- # clojure-boston (2)
- # clojure-italy (21)
- # clojure-nl (8)
- # clojure-spec (7)
- # clojure-uk (94)
- # clojurescript (126)
- # clojutre (7)
- # core-async (3)
- # cursive (7)
- # data-science (1)
- # datascript (4)
- # datomic (6)
- # duct (1)
- # emacs (19)
- # figwheel (1)
- # fulcro (31)
- # graphql (13)
- # jobs (5)
- # jobs-discuss (42)
- # keechma (4)
- # leiningen (10)
- # luminus (3)
- # mount (2)
- # nyc (3)
- # off-topic (37)
- # om-next (3)
- # onyx (45)
- # pedestal (2)
- # re-frame (4)
- # reagent (2)
- # reitit (16)
- # shadow-cljs (118)
- # spacemacs (10)
- # tools-deps (8)
- # vim (20)
@parameme fyi the realworld api implementation is here https://github.com/walkable-server/realworld It's almost complete

@tony.kay had you done async testing with fulcro-spec? I'm doing some experimenting
this works:
(deftest card-widget
(async done
(is (= 1 2))
(done)))
but this doesnt:
(specification "card widget"
(async done
(is (= 1 2))
(done)))
(`async` is been pulled from cljs.test
)
I want to do some interaction testing, and that will probably require some async things, because for mounting a fulcro app for example, I have to rely on a callback to know it's ready to use
but not sure why it wouldn’t work…it is just a deftest…unless it works by somehow throwing special exceptions
yeah, it seems like its been ignored or something, the test doesn't fail
I mean, testing in general, there is a mixed bag of things
and I wanna experiment with interaction testing to see how it goes
you’d have to dig into the source of async and see what it does…specification is a deftest whose body is wrapped for catching exceptions
humm, I guess for now I'll just use deftest
for those
the async must be returning something special
and by catching it might be breaking it?
actually, it is asynchronous, so the reporting is probably happening after Fulcro spec’s collection has finished
but fulcro uses same as cljs.test for flow right?
also, I get correct reporting when using deftest
I'm not running there, I'm running in a karma terminal
I'm in a half baked setup, so I'm running on console at this point
but I think I can try that, let me check how it would go in the outline view
so, Fulcro specification
emits a deftest…it’s a small macro. don’t fear looking at the source. Fulcro’s runner just calls cljs.test run-all-tests with a regex
@tony.kay just tested the async, the main outline fails, but the error is not shown =/