This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-28
Channels
- # aleph (1)
- # announcements (16)
- # bangalore-clj (1)
- # beginners (78)
- # cider (109)
- # clara (3)
- # cljdoc (6)
- # cljsjs (3)
- # clojure (209)
- # clojure-dev (11)
- # clojure-europe (1)
- # clojure-france (9)
- # clojure-italy (13)
- # clojure-nl (3)
- # clojure-spain (2)
- # clojure-spec (19)
- # clojure-uk (50)
- # clojurescript (41)
- # clojutre (2)
- # core-async (45)
- # cursive (2)
- # datomic (14)
- # emacs (6)
- # figwheel-main (1)
- # fulcro (101)
- # graalvm (1)
- # graphql (3)
- # jobs-discuss (3)
- # kaocha (12)
- # leiningen (8)
- # music (4)
- # off-topic (47)
- # parinfer (8)
- # pathom (17)
- # pedestal (53)
- # re-frame (47)
- # reagent (22)
- # reitit (4)
- # shadow-cljs (49)
- # tools-deps (87)
I was looking at integrating eastwood with junit XML
which would allow to have a nice error report in CircleCI for example
but I was wondering if maybe instead of doing that, I could do a Kaocha plugin
they are not really tests though, not sure how well it would fit in Kaocha something like that
looking at eastwood I think it could make sense, it would be a test type (test suite type) rather than a plugin. but you would have to pick their API apart a bit to have separate load/run stages
that or you can rip off kaocha-junit's output code and hook it up to eastwood directly 😉
(not that I *don't* want to discourage you, but it would be a bit of work to write a test type for this, depending on how well you are familiar with eastwood's internals and kaocha test types)
yeah not super familiar with either, and I guess it might involve some changes in eastwood itself
I can add it there as an issue to see if the maintainer is interested
we would get the junit support for free though with that which would be nice