@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 don’t introduce asynchrony into unit tests. I mock it out…so, no

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

“some interaction testing”…in unit tests?

yup

I mean, testing in general, there is a mixed bag of things

good luck…I’ve never gotten anything useful out of testing that way…just pain

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

might be a special exception that needs to be let through?

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

you get correct reporting in the outline for fulcro spec?

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

the macros add in a few extra calls to reporting to make the outline nest and such

but yes, it is meant to be just clj(s).test for compatibility

@tony.kay just tested the async, the main outline fails, but the error is not shown =/