summaryrefslogtreecommitdiff
path: root/PULL_REQUEST_TEMPLATE.md
diff options
context:
space:
mode:
authorw0rp <devw0rp@gmail.com>2018-05-15 13:14:20 +0100
committerw0rp <devw0rp@gmail.com>2018-05-15 13:14:28 +0100
commit4a76cb0dd5a9056a9616413ac59c16705788bb0e (patch)
tree88e11467469cf96b9c3c698c00820fda0dea9b16 /PULL_REQUEST_TEMPLATE.md
parent38c66d33fe8022803497c49239b06112ccbd0a83 (diff)
downloadale-4a76cb0dd5a9056a9616413ac59c16705788bb0e.zip
Update the issue template to tell you where to find command callback tests
Diffstat (limited to 'PULL_REQUEST_TEMPLATE.md')
-rw-r--r--PULL_REQUEST_TEMPLATE.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md
index 94116532..e1ca94f6 100644
--- a/PULL_REQUEST_TEMPLATE.md
+++ b/PULL_REQUEST_TEMPLATE.md
@@ -12,7 +12,8 @@ READ THIS: Before creating a pull request, please consider the following first.
that ALE can work with, please add Vader tests for them. Look at existing
tests in the test/handler directory, etc.
* If you add or modify a function for computing a command line string for
- running a command, please add Vader tests for that.
+ running a command, please add Vader tests for that. Look at existing
+ tests in the test/command_callback directory, etc.
* Generally try and cover anything with Vader tests, although some things just
can't be tested with Vader, or at least they can be hard to test. Consider
breaking up your code so that some parts can be tested, and generally open up