dev: refine test launcher #506
Comments
lread
added a commit
to lread/etaoin
that referenced
this issue
Dec 2, 2022
The new test:bb and test:jvm bb tasks replace the test task. I think this makes bb and jvm platform tests easier to discover. Extracted out test matrix generation to its own test-matrix bb task (was formerly invoked via a test task cmd line arg). Now employing babashka cli for test tasks. Using for both test:jvm and test:bb. Can now choose to run individual tests vars and namespaces. Our test tasks now accept --nses --patterns and --vars options which we pass thru to the cognitect test runner. Updates to babashka allow us to now no longer rely on babashka: - namespace fork (was need for test runner) - babashka spec.alpha fork (ide feature relies on spec.alpha). Closes clj-commons#507 For consitency: - dev task renamed to dev:jvm - dev-bb task renamed dev:bb. Adjusted this one to match test:bb re classpath construction. When I sent in my own --classpath I think Clojure's spec.alpha was getting in the way. Now explicitly relying on slingshot. Closes clj-commons#511 Docker run task corrected to accept args. User and dev guides updated accordingly. Closes clj-commons#506
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
Granularity of test launching is coarse.
I can run a suite:
api,ide, orunit.These suites take a long while to run.
This makes quick verification of a single test painful.
But I'd like to
Be able to run a single test.
Notes
I'll take advantage of the recent test runner support in babashka.
The text was updated successfully, but these errors were encountered: