diff options
Diffstat (limited to 'doc/guides/writing-tests.md')
| -rw-r--r-- | doc/guides/writing-tests.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/guides/writing-tests.md b/doc/guides/writing-tests.md index 1fa2b3c558..b2cd8ed8b2 100644 --- a/doc/guides/writing-tests.md +++ b/doc/guides/writing-tests.md @@ -306,12 +306,14 @@ the upstream project, send another PR here to update Node.js accordingly. Be sure to update the hash in the URL following `WPT Refs:`. ## C++ Unit test + C++ code can be tested using [Google Test][]. Most features in Node.js can be tested using the methods described previously in this document. But there are cases where these might not be enough, for example writing code for Node.js that will only be called when Node.js is embedded. ### Adding a new test + The unit test should be placed in `test/cctest` and be named with the prefix `test` followed by the name of unit being tested. For example, the code below would be placed in `test/cctest/test_env.cc`: @@ -345,18 +347,21 @@ static void at_exit_callback(void* arg) { ``` Next add the test to the `sources` in the `cctest` target in node.gyp: + ```console 'sources': [ 'test/cctest/test_env.cc', ... ], ``` + Note that the only sources that should be included in the cctest target are actual test or helper source files. There might be a need to include specific object files that are compiled by the `node` target and this can be done by adding them to the `libraries` section in the cctest target. The test can be executed by running the `cctest` target: + ```console $ make cctest ``` |