Skip to content

Commit b00a0f0

Browse files
committed
[Docs] Add a bit more structure to the test runner configuration section
1 parent 92337ac commit b00a0f0

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

doc/modules/ROOT/pages/testing/running_tests.adoc

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,8 @@ kbd:[C-c C-t t] or kbd:[C-c C-t C-t].
8383

8484
You can configure CIDER's test execution behavior in multiple ways.
8585

86+
=== Test Namespace Naming Convention
87+
8688
If your tests are not following the `some.ns-test` naming convention
8789
you can set the variable `cider-test-infer-test-ns` to a function that
8890
takes the current namespace and returns the matching test namespace
@@ -105,12 +107,17 @@ This uses the convention of prepending 'test-' to the namespace name."
105107
(setq cider-test-infer-test-ns #'cider-custom-test-ns-fn)
106108
----
107109

110+
=== Macros Used to Define Tests
111+
108112
If your individual tests are not defined by `deftest` or `defspec`, CIDER will
109113
not recognize them when searching for a test at point in `cider-test-run-test`.
110114
You can customize the variable `cider-test-defining-forms` to add additional
111115
forms for CIDER to recognize as individual test definitions.
112116

113-
If you want to view the test report regardless of whether the tests have
117+
=== Display Test Report on Success
118+
119+
By default the test report is displayed only when there are test failures or
120+
errors. If you want to view the test report regardless of whether the tests have
114121
passed or failed:
115122

116123
[source,lisp]

0 commit comments

Comments
 (0)