summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorw0rp <devw0rp@gmail.com>2021-03-21 00:21:49 +0000
committerw0rp <devw0rp@gmail.com>2021-03-21 00:25:33 +0000
commitf7852dbd0a063d6d82ee17a5057fea53cb79b21d (patch)
tree00b98a3c668af9313eedd6936475c81eeef7e9b8 /doc
parent35caaecc9fc5822f0474e913d0b7655048fd30ee (diff)
downloadale-f7852dbd0a063d6d82ee17a5057fea53cb79b21d.zip
#3633 - Move linter tests into test/linter
Diffstat (limited to 'doc')
-rw-r--r--doc/ale-development.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ale-development.txt b/doc/ale-development.txt
index 3436b531..7f8ec28f 100644
--- a/doc/ale-development.txt
+++ b/doc/ale-development.txt
@@ -181,7 +181,7 @@ Generally write tests for any changes you make. The following types of tests
are recommended for the following types of code.
* New/edited error handler callbacks -> Write tests in `test/handler`
-* New/edited command callbacks -> Write tests in `test/command_callback`
+* New/edited linter definition -> Write tests in `test/linter`
* New/edited fixer functions -> Write tests in `test/fixers`
Look at existing tests in the codebase for examples of how to write tests.
@@ -278,8 +278,8 @@ be written like so. >
\ '1:Something went wrong',
\ ]
<
-Tests for what ALE runs should go in the `test/command_callback` directory,
-and should be written like so. >
+Tests for what ALE runs should go in the `test/linter` directory, and should
+be written like so. >
Before:
" Load the linter and set up a series of commands, reset linter variables,