lambdaisland / lambdaisland/kaocha
Suggestion: Run reloaded tests first
Open
Nobody has claimed this yet.
improvement
- Dominant language
- Clojure
- Stars
- 860
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
[watch] Reloading #{norled.vessel.c4.refiners.scheduled-route-test}
[(.....................................................................................................................)(.)(.........)(.)(.)(.)()()(.)(.)(................)(...)(.)(.)(.)(.)(...........)(.)(.)(..............)(.)(.)(.)(..........)(......)(.........................................................................................)(.)(.)(............................................................................................................................................................................................................................................................................)(....)(.)(......)(........)(...........................)(...................................)(.)(................................)(.........)(..............................................................................)(.)(.)(.)(.)(..)()(..................)(....)(.....)(.....................................................................)(.............)(.)(........)(...........................................................................)(..)(.)(........)(.)(............................)(..)(...)(.)(..)(....)()(.)(...........................................................)(.............)(..)(.....)(.)(.)(.)(.)(.)(.)(.....)(.................)(.)(.)(.)(..)(.....)(.)(....)(.)(E)(.)(.)(.)(.)(.)(.)(.....)(..)(.)(.....)(.................)(...)(..............................................)(..)(.......)(.......)(..................................................................................)(...)(...)(.......................................)]
341 tests, 1365 assertions, 1 errors, 0 failures.
When watch reloads test namespaces, it would be nice if it ran those tests first. This would enable a faster workflow.
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
Start by tracing the watch reload handling for test namespaces, using the displayed reload output and the scheduled-route-test namespace as the entry point. Determine how the current test queue is built, then verify that reloaded namespaces run before the remaining tests and that the faster workflow is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100