This repository was archived by the owner on Oct 28, 2024. It is now read-only.
Open
Conversation
added 10 commits
May 1, 2020 18:20
This behaviour is the same as with Leiningen's test selectors.
When tests are run via test-ns-hook, clojure.test calls:
(do-report {:type :begin-test-var, :var v})
(inc-report-counter :test)
Which for circleci.test reports means that the test counter is
incremented twice.
This behaviour is similar to Leiningen and Clojure test where if a test calls another test, the once and each fixtures are called only once.
This is in accordance with clojure.test's definition of fixtures and test-ns-hook: Note: Fixtures and test-ns-hook are mutually incompatible. If you are using test-ns-hook, fixture functions will *never* be run. Global fixtures still run.
Author
|
Any update on this? 😄 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mainly for running individual tests from the commandline #2
Some additional fixes: