This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-03
Channels
- # admin-announcements (2)
- # arachne (1)
- # architecture (6)
- # boot (316)
- # cider (7)
- # cljsrn (7)
- # clojure (169)
- # clojure-argentina (3)
- # clojure-belgium (1)
- # clojure-canada (4)
- # clojure-india (1)
- # clojure-russia (39)
- # clojure-spec (27)
- # clojure-uk (55)
- # clojurescript (213)
- # css (1)
- # cursive (20)
- # datavis (2)
- # datomic (52)
- # devcards (3)
- # dirac (78)
- # emacs (20)
- # events (1)
- # funcool (3)
- # hoplon (15)
- # jobs-rus (2)
- # om (57)
- # onyx (82)
- # overtone (1)
- # re-frame (10)
- # reagent (1)
- # ring-swagger (46)
- # spacemacs (7)
- # specter (31)
- # spirituality-ethics (1)
- # sql (43)
- # test-check (1)
- # testing (4)
- # untangled (30)
Answer: it’s painful… https://github.com/jaycfields/expectations/issues/70#issuecomment-237113313
I love how terse Expectations is but the lack of fixed symbol names causes all sorts of problems that the other test libraries just don’t have. In addition, Expectations does a fair bit of "magic" for its fixtures support (it loads a fixed namespace automatically behind the scenes) and when it does a test run — over one or more namespaces — it also does a fair bit of setup and teardown which makes it even harder to shoehorn into the model of pulling a bunch of :test
metadata and just running functions...
I’ll probably have another run at it, but maybe not until next week (perhaps after I’ve gotten some feedback from folks on that ticket).