Testing Node.js
With JetBrains Rider, you can test Node.js applications using numerous frameworks. Since May 2018, Nodeunit is deprecated. See the Nodeunit official website for details.
Before you start
Make sure the Node.js plugin is enabled on the Settings/Preferences | Plugins page, tab Installed, see Managing plugins for details.
Download and install a testing framework.
Creating and running unit tests for Node.js applications
To have JetBrains Rider recognize the unit tests and detect the corresponding production source code, mark the folder where the unit tests are stored as a test folder.
Create a run configuration of the type Nodeunit.
Launch unit tests and monitor test results in the Run tool window.
Creating Nodeunit tests
Create a folder test at the same level as the src folder
Populate the test folder. For each production file, create a separate test file.
Mark the folder where the tests are stored as test folder.
Creating a Nodeunit run configuration
Open the Run/Debug Configuration dialog by choosing from the main menu.
Click the Add button
on the toolbar and select the Nodeunit configuration type.- In the dialog that opens, specify the following:
The name to identify the configuration.
Specify the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux.
The working directory. This can be the project root folder or the parent directory for the test folder.
- The scope of tests to run.
To have JetBrains Rider run all the test files in a folder, choose All JavaScript test files in the directory from the Run list. In the Directory field, provide the path to the test folder relative to the working directory.
To have a specific test executed, choose JavaScript test file from the Run list. In the JavaScript test file field, provide the path to the file relative to the working directory.
Apply the changes and close the dialog.