Skip to content
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions BUILDING.md
Original file line number Diff line number Diff line change
Expand Up @@ -317,37 +317,39 @@ To run the linter without running tests, use
If you are updating tests and want to run tests in a single test file
(e.g. `test/parallel/test-stream2-transform.js`):

```text
$ tools/test.py test/parallel/test-stream2-transform.js
```
````text
$ python3 tools/test.py test/parallel/test-stream2-transform.js
Comment thread
tony-go marked this conversation as resolved.
Outdated

Comment thread
tony-go marked this conversation as resolved.
Outdated

You can execute the entire suite of tests for a given subsystem
by providing the name of a subsystem:

```text
$ tools/test.py child-process
```
$ python3 tools/test.py child-process
````
Comment thread
tony-go marked this conversation as resolved.
Outdated

You can also execute the tests in a test suite directory
(such as `test/message`):

```text
$ tools/test.py test/message
$ python3 tools/test.py test/message
```

If you want to check the other options, please refer to the help by using
the `--help` option:

```text
$ tools/test.py --help
$ python3 tools/test.py --help
```

You can usually run tests directly with node:

```text
$ ./node ./test/parallel/test-stream2-transform.js
$ ./node test/parallel/test-stream2-transform.js
Comment thread
tony-go marked this conversation as resolved.
```

> Info: `./node` points to your local Node.js build.

Remember to recompile with `make -j4` in between test runs if you change code in
the `lib` or `src` directories.

Expand Down