Clojure
ClojureScript brings Clojure's testing model to the browser and Node.js. The testing primitives — deftest, is, testing — work identically to Clojure. But the runtime environment is different: no JVM, different async semantics, and multiple possible test targets. shadow-cljs makes all of this manageable with a single configuration file.
Clojure
re-frame's unidirectional data flow — events → effects → db → subscriptions → views — makes applications predictable. It also makes them testable. Every piece of behavior in a re-frame app is a pure function or a data-driven side effect description. re-frame-test provides the tooling to test them without a running browser. What re-frame-test
Clojure
Example-based tests check specific cases. Property-based tests check invariants across hundreds of randomly generated inputs. test.check is Clojure's property testing library — a port of Haskell's QuickCheck — and it finds bugs that no developer thought to test for. Why Property-Based Testing Consider a sorting function. Example-based
Clojure
Kaocha is the most flexible test runner in the Clojure ecosystem. While lein test and clojure -M:test get you started, Kaocha gives you fine-grained control over test selection, execution order, output formatting, and extensibility through plugins. This guide covers advanced Kaocha configuration for teams that need more than defaults.
Clojure
Babashka is a native Clojure scripting runtime that starts in milliseconds. It runs Clojure code without the JVM startup penalty, making it practical for scripts that need to run frequently — build tools, CI helpers, file processors, HTTP clients. But scripts grow complex, and complex code needs tests. This guide covers
Clojure
Clojure's testing ecosystem is unusually rich for a language its size. At the foundation sits clojure.test, included in the standard library and requiring no dependencies. On top of that, Midje adds a readable BDD-style syntax with powerful stubbing. And test.check brings property-based testing — Clojure's