summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorSantiago Gimeno <santiago.gimeno@gmail.com>2016-05-26 02:33:21 +0200
committerRod Vagg <rod@vagg.org>2016-06-02 22:42:01 +1000
commitb2c7d466d471c040bdd5463bde3dbba62246502a (patch)
tree39a3233d589bf7a5adb9f3ce56b6382e82bc0272 /CONTRIBUTING.md
parentb23cd48ca00115fd7d35b3fd45435dacba8317c4 (diff)
downloadnode-new-b2c7d466d471c040bdd5463bde3dbba62246502a.tar.gz
doc,test: add `How to write a Node.js test` guide
PR-URL: https://github.com/nodejs/node/pull/6984 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Yorkie Liu <yorkiefixer@gmail.com>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b9e495e9b9..77167659f4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -133,8 +133,9 @@ $ git rebase upstream/master
### Step 5: Test
Bug fixes and features **should come with tests**. Add your tests in the
-test/parallel/ directory. Look at other tests to see how they should be
-structured (license boilerplate, common includes, etc.).
+`test/parallel/` directory. For guidance on how to write a test for the Node.js
+project, see this [guide](./doc/guides/writing_tests.md). Looking at other tests
+to see how they should be structured can also help.
```text
$ ./configure && make -j8 test