From ebe6d672541b3e4ee3223716c2d677558c6cf2d8 Mon Sep 17 00:00:00 2001 From: Noah Bogart Date: Mon, 21 Oct 2024 12:59:52 -0400 Subject: [PATCH] Clarify position on Clojurescript --- README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2e7405d..f7a03c5 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,7 @@ An alternative to `clojure.test`, aiming to be feature-rich and easily extensibl - [Getting Started](#getting-started) - [Why a new test framework?](#why-a-new-test-framework) +- [Why no Clojurescript/other flavors?](#why-no-clojurescriptother-flavors) - [Usage](#usage) - [Writing tests with Lazytest](#writing-tests-with-lazytest) - [Partitioning Individual Tests and Suites](#partitioning-individual-tests-and-suites) @@ -108,6 +109,10 @@ Other alternatives such as [Midje][midje], [classic Expectations][expectations v I like the ideas put forth in Alessandra's post above about Lazytest and hope to experiment with achieving them 14 years later, while borrowing heavily from the work in both the Clojure community and test runners frameworks in other languages. +## Why no Clojurescript/other flavors? + +I am not nearly familiar enough with other flavors of Clojure and don't have the bandwidth to support them. If someone from the community is willing to steward that work, I'm open to adding support. + ## Usage With the above `:test` alias, call `clojure -M:test [options]` to run your test suite once, or `clojure -M:test [options] --watch` to use "Watch mode" (see below) to run repeatedly as files change. @@ -420,7 +425,7 @@ This will run: ``` ```` -Whereas these will not (first is skipped, second isn't Clojure): +Whereas these will not (first is skipped, second isn't "clojure" or "clj"): ````markdown ```clojure lazytest/skip=true @@ -428,7 +433,7 @@ Whereas these will not (first is skipped, second isn't Clojure): ;; => exit!!! ``` -```python +```clojurescript print("Hello world!") ``` ````