Tensegritics / Tensegritics/ClojureDart
Hot testing
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1.6k
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
Working with Clojure's Kaocha or the shadow-cljs test runner, it's very convenient that I can have it "watch" tests.
My image of how it works: when a source file (namespace) is changed, it finds all tests that use any of the namespaces that require the changed namespace, and run all the tests involved on every change.
I don't know how they deal with the case when a file is saved so quickly in succession that tests don't have time to run to completion. Possibly interrupt the previous execution?
Ref.
- configuration in kaocha
- in shadow-cljs you need to have a separate build (eg
:tests) for testing and then you canshadow-cljs watch teststhat (relevant config docs)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start with the linked Kaocha watch-mode and shadow-cljs testing documentation, then determine how this project could track namespace dependencies and handle rapid successive saves; done means an agreed and tested hot-testing workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100