This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-09
Channels
- # announcements (4)
- # beginners (71)
- # boot (258)
- # braid-chat (7)
- # business (3)
- # cider (5)
- # cljs-dev (5)
- # cljsrn (64)
- # clojure (154)
- # clojure-canada (1)
- # clojure-poland (112)
- # clojure-russia (290)
- # clojurebridge (1)
- # clojurescript (60)
- # community-development (1)
- # core-async (25)
- # cursive (9)
- # data-science (1)
- # datomic (40)
- # editors (14)
- # events (2)
- # hoplon (2)
- # jobs (3)
- # ldnclj (51)
- # lein-figwheel (2)
- # luminus (1)
- # off-topic (5)
- # om (57)
- # onyx (29)
- # overtone (1)
- # parinfer (52)
- # portland-or (1)
- # proton (17)
- # quil (2)
- # re-frame (77)
- # reagent (1)
- # ring-swagger (20)
- # spacemacs (1)
- # test-check (4)
- # testing (13)
- # yada (1)
@paulspencerwilliams: what solution did you end up with, and were you satisfied with the result?
Hi @lucasbradstreet, in the end, I used a combination of roundtripping tests for majority of coverage backed by example based tests for confidence. I will reduce these examples to a couple when I get back to tidying the code. I promised a blog post, and one is in draft although it maybe the weekend before I get chance to revisit it but I really enjoyed the exercise. Satified? I'm not sure, I liked the example based backups atm, but I think that will dissappear as I start to explore more. I can imagine using test.check more as I move my workflow from TDD, to repl driven. https://github.com/paulspencerwilliams/gormanic/blob/master/test/gormanic/core_test.clj
Cool. Was curious
I usually pepper in a few example based tests as a sanity check