This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-08
Channels
- # adventofcode (9)
- # announcements (5)
- # babashka (3)
- # beginners (46)
- # calva (21)
- # cider (15)
- # clj-kondo (20)
- # cljs-dev (57)
- # cljsrn (10)
- # clojure (147)
- # clojure-dev (6)
- # clojure-europe (3)
- # clojure-france (2)
- # clojure-italy (8)
- # clojure-nl (18)
- # clojure-norway (5)
- # clojure-spec (16)
- # clojure-uk (63)
- # clojuredesign-podcast (7)
- # clojurescript (65)
- # clojurex (42)
- # cursive (12)
- # datomic (10)
- # fulcro (47)
- # graalvm (102)
- # graphql (2)
- # jobs (5)
- # joker (12)
- # off-topic (33)
- # pedestal (6)
- # re-frame (6)
- # reagent (8)
- # reitit (6)
- # remote-jobs (4)
- # rewrite-clj (10)
- # shadow-cljs (86)
- # sql (45)
- # testing (4)
- # tools-deps (43)
- # vim (8)
- # xtdb (3)
@tws have a look at https://cljdoc.org/d/lambdaisland/kaocha/0.0-367/doc/7-plugins#profiling
if you want to do custom processing on the timing information you can gather them up in a post-run hook
(ns kaocha-demo.hooks
(:require [kaocha.testable :as testable]
[kaocha.hierarchy :as hierarchy]))
(def post-run [test-result]
(spit "timing.edn"
(pr-str
(into {}
(comp (filter hierarchy/leaf?)
(map (juxt ::testable/id :kaocha.plugin.profiling/duration)))
(testable/test-seq test-result))))
test-result)