diff options
| author | Bozhidar Batsov <bozhidar@batsov.com> | 2016-04-13 08:59:52 -0700 |
|---|---|---|
| committer | Bozhidar Batsov <bozhidar@batsov.com> | 2016-04-13 09:00:23 -0700 |
| commit | f9b1b45c5e62213d76e45db36c325d05514d36f6 (patch) | |
| tree | d130c2969f8a3536d49ffcbfe3dbd720c0989238 /doc/running_tests.md | |
| parent | 0e52e3adbc8fcbcfc459273f6be5119a2fd0e3eb (diff) | |
Use one lever bigger headings everywhere in the manual
Diffstat (limited to 'doc/running_tests.md')
| -rw-r--r-- | doc/running_tests.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/running_tests.md b/doc/running_tests.md index d69ac972..cc423a74 100644 --- a/doc/running_tests.md +++ b/doc/running_tests.md @@ -1,4 +1,4 @@ -### Running tests +## Running tests You can run `clojure.test` tests pretty quickly in CIDER. Pressing <kbd>C-c C-t n</kbd> or <kbd>C-c C-t C-n</kbd> in a source buffer or a REPL buffer will run @@ -42,7 +42,7 @@ passed or failed: (setq cider-test-show-report-on-success t) ``` -#### Running tests automatically (test-driven development) +### Running tests automatically (test-driven development) CIDER provides a minor-mode that automatically runs all tests for a namespace whenever you load a file (with <kbd>C-c C-k</kbd>). You can toggle it @@ -56,7 +56,7 @@ This is completely equivalent to manually typing <kbd>C-c C-t C-n</kbd> every time you load a Clojure buffer. Also, as described above before, CIDER is smart enough to figure out the namespace containing the tests. -#### Using cider-test with alternative test libraries +### Using cider-test with alternative test libraries The `clojure.test` machinery is designed to be pluggable. Any test library can implement it if so desired, and therefore leverage `cider-test`. For |