Jasmine Test Explorer for Visual Studio Code

Run your Jasmine tests in Node using the Test Explorer UI.

Features

Shows a Test Explorer in the Test view in VS Code's sidebar with all detected tests and suites and their state
Adds CodeLenses to your test files for starting and debugging tests
Adds Gutter decorations to your test files showing the tests' state
Adds line decorations to the source line where a test failed
Shows a failed test's log when the test is selected in the explorer
Lets you choose test suites or individual tests in the explorer that should be run automatically after each file change
Forwards the console output from Jasmine to a VS Code output channel

Getting started

Install the extension
Restart VS Code and open the Test view
Run / Debug your tests using the / icons in the Test Explorer or the CodeLenses in your test file

Configuration

The following configuration properties are available:

Property	Description
`jasmineExplorer.config`	The location of the Jasmine config file (relative to the workspace folder) (default: `spec/support/jasmine.json`)
`jasmineExplorer.env`	Environment variables to be set when running the tests
`jasmineExplorer.nodePath`	The path to the node executable to use. By default it will attempt to find it on your PATH, if it can't find it or if this option is set to `null`, it will use the one shipped with VS Code
`jasmineExplorer.nodeArgv`	The arguments to the node executable to use. To enable automatic typescript, import ts-node package and use these arguments: ["--require", "ts-node/register"]
`jasmineExplorer.debuggerPort`	The port for running the debug sessions (default: `9229`)
`jasmineExplorer.breakOnFirstLine`	Setting to `true` injects a breakpoint at the first line of your test, (default: `false`)
`testExplorer.codeLens`	Show a CodeLens above each test or suite for running or debugging the tests
`testExplorer.gutterDecoration`	Show the state of each test in the editor using Gutter Decorations
`testExplorer.onStart`	Retire or reset all test states whenever a test run is started
`testExplorer.onReload`	Retire or reset all test states whenever the test tree is reloaded

Commands

The following commands are available in VS Code's command palette, use the ID to add them to your keyboard shortcuts:

ID	Command
`test-explorer.reload`	Reload tests
`test-explorer.run-all`	Run all tests
`test-explorer.run-file`	Run tests in current file
`test-explorer.run-test-at-cursor`	Run the test at the current cursor position
`test-explorer.cancel`	Cancel running tests

Troubleshooting

All console output from Jasmine is forwarded to a VS Code output channel called "Jasmine Tests", this is often useful in tracking down problems.

If the "Jasmine Tests" output channel doesn't show up, the Test view doesn't show your tests or anything else doesn't work as expected (and can't be explained from Jasmine's console output), you can turn on diagnostic logging using one of the following configuration options (note: in multi-root workspaces, these options are always taken from the first workspace folder):

jasmineExplorer.logpanel: Write diagnotic logs to an output panel called "Jasmine Explorer Log"
jasmineExplorer.logfile: Write diagnostic logs to the given file

There is a bug in Node >= 10.6 that breaks this adapter. If you're using a version of Node affected by this bug, add "jasmineExplorer.nodePath": null to your configuration as a workaround.