@@ -54,17 +54,21 @@ by a source file or by the REPL, using kbd:[C-c C-t n] or
5454kbd:[C-c C-t C-n]. Note that it's idiomatic for Clojure projects
5555to locate tests in a separate namespace than the code that is being
5656tested. CIDER uses a simple algorithm to figure out where the tests
57- are located. The algorithm works as follows. If you're in an
58- implementation namespace (e.g. `some.ns`), CIDER will try to find a
57+ are located. The algorithm works as follows:
58+
59+ * If you're in an implementation namespace (e.g. `some.ns`), CIDER will try to find a
5960matching test namespace (by default `some.ns-test`) and run the tests
60- there. But if you're in something that already looks like a test
61+ there.
62+ * If you're in something that already looks like a test
6163namespace (e.g. `some.ns-test`), CIDER will simply run the tests in
62- that namespace. If you have put some of your tests into your
63- implementation namespace, using `clojure.test/with-test`, for
64- instance, you might want to suppress the namespace inference logic and
65- force CIDER to run tests in the current namespace unconditionally.
66- You can do this by adding a prefix to the namespace commands: kbd:[C-u C-c C-t C-n]. This will simply run whatever tests are present in
67- the currently visited or active namespace.
64+ that namespace.
65+
66+ TIP: If you have put some of your tests into your implementation namespace, using
67+ `clojure.test/with-test`, for instance, you might want to suppress the namespace
68+ inference logic and force CIDER to run tests in the current namespace
69+ unconditionally. You can do this by adding a prefix to the namespace commands:
70+ kbd:[C-u C-c C-t C-n]. This will simply run whatever tests are present in the
71+ currently visited or active namespace.
6872
6973You can also run a subset of the tests defined in the namespace,
7074filtered by test selectors, using kbd:[C-c C-t C-s]. CIDER will
0 commit comments