@clojurians.net Not sure what you did to the reporting, but Iām very pleased. Fulcro-spec (when mocking) checks specs, and in earlier versions the reporting was all hosed and you could not tell what was wrong. Now I get a really nice error:
for a test like this:
(>defn sample [x]
[int? => int?]
x)
(>defn f [x]
[int? => int?]
(sample :x)
x)
(specification "Instrument tests"
(when-mocking!
(sample n) => n
(assertions
"Sample does stuff"
(f 33) => 33)))
which makes the testing experience much nicer. Thanks for the improvements.A combination of making reporting work in a REPL/non-browser-JS-console environment and overriding the spec-printer with expound
by default, so in this case I'm guessing it's the latter. Glad it's working for you!