diff options
| author | John MacFarlane <jgm@berkeley.edu> | 2019-07-19 09:24:31 -0700 |
|---|---|---|
| committer | John MacFarlane <jgm@berkeley.edu> | 2019-07-19 09:24:31 -0700 |
| commit | d4b2128d55f558069fb9ba88bb6cae534da98151 (patch) | |
| tree | 9f332ea937fc55e98ba3eb6c11f6d7ee10ced61d /CONTRIBUTING.md | |
| parent | 145b4d5ad654a89f2dd9749b3b1774400373b792 (diff) | |
| download | pandoc-d4b2128d55f558069fb9ba88bb6cae534da98151.tar.gz | |
CONTRIBUTING.md: mention command tests.
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6766b37e4..b2cf63c3b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -185,7 +185,8 @@ the pattern of the existing tests. The test suite code is in probably easiest to add some data files to the `test` directory, and modify `test/Tests/Old.hs`. Otherwise, it is better to modify the module under the `test/Tests` hierarchy corresponding to the pandoc module you -are changing. +are changing. Alternatively, you may add a "command test" to +the `/test/command/` hierarchy, following the pattern of the tests there. For `docx` tests, you can rebuild the golden tests by passing `--accept` to the test script (so if you're using stack, |