This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-18
Channels
- # announcements (4)
- # babashka (2)
- # beginners (72)
- # calva (2)
- # cider (18)
- # clj-kondo (30)
- # cljs-dev (2)
- # clojure (106)
- # clojure-austin (2)
- # clojure-europe (17)
- # clojure-italy (6)
- # clojure-nl (4)
- # clojure-uk (109)
- # clojurescript (31)
- # cursive (6)
- # data-science (2)
- # datomic (30)
- # events (1)
- # fulcro (20)
- # graphql (4)
- # jobs (2)
- # joker (8)
- # kaocha (2)
- # meander (31)
- # off-topic (1)
- # pathom (53)
- # re-frame (22)
- # reitit (1)
- # shadow-cljs (26)
- # specter (2)
- # sql (20)
- # testing (2)
- # tools-deps (2)
- # tree-sitter (1)
- # xtdb (20)
- # yada (6)
I have an app that sends some messages to the outside world, and I'd like to generate a file that has examples of these messages for the purpose of documentation. (As a secondary goal, I'd also like to validate that these messages conform to a set of specs, and fail a test if they don't.) My thought is to write a test that generates the file as a side effect, and I imagine I can get it to work with a fair bit of manual hacking but I'm wondering if there's a library or common pattern for doing this already.
I feel like I'm a little off the beaten testing path since most test runners report when a test fails, but I want to generate some output when the test succeeds as a kind of living documentation of the current behavior. This seems to fit the same niche as a test coverage file I suppose.