Interacting with Test Result Reports

Should tests fail then CIDER displays a test result report in the *cider-test-report* buffer. This buffer uses cider-test-report-mode, which makes it easy to review any failures that might have occurred and jump directly to the definition of failing tests.

Calling test commands again will update the test report.

You can also configure test reports to be displayed on success.
Keyboard shortcut Command name Description

g

cider-test-run-test

Run test at point.

n

cider-test-run-ns-tests

Run tests for current namespace.

s

cider-test-run-ns-tests-with-filters

Run tests for current namespace with selector filter.

l

cider-test-run-loaded-tests

Run tests for all loaded namespaces.

p

cider-test-run-project-tests

Run tests for all project namespaces. This loads the additional namespaces.

f

cider-test-rerun-failed-tests

Re-run test failures/errors.

M-p

cider-test-previous-result

Move point to previous test.

M-n

cider-test-next-result

Move point to next test.

t or M-. or kbd:click

cider-test-jump

Jump to test definition.

d

cider-test-ediff

Display diff of actual vs expected.

e

cider-test-stacktrace

Display test error cause and stacktrace info.

Most key bindings are defined in cider-test-report-mode-map, while the click behavior is defined in cider-test-var-keymap.