v1.6.3

This release reverts the use of a TS server plugin from 1.6.2. It seems like there are outstanding issues, and I don't know how to fix them. The documentation how to do this kind of thing is effectively non-existent and I don't feel able to supporting it; the green tests made me too confident. I will explore a tree-sitter approach (or swc or something along those lines.)

Full Changelog: v1.6.2...v1.6.3

v1.6.2

This release uses a TypeScript server plugin in VS Code's TypeScript Language Features to implement parsing of test files. This fixes issues where the simple JavaScript parser did not work, and should generally be more efficient as it reuses the language information VS Code already has in memory.

If you encounter problems with this release, you can revert to the old logic by setting "nodejs-testing.useTypescriptServer": false in your settings. If this resolves your problem, please make sure to open an issue, as I otherwise intend to remove this option in a later release.

v1.6.1

This release adds support for Node.js snapshot testing.

You are given the option to make a new snapshot file as needed:

...or update it...

...and once you do, tests should be green.

The extension adds the --experimental-test-snapshots flag automatically, so no extra configuration is needed.

v1.6.0

This release adds support for rich stack traces in test failures, adopting the new VS Code API to do so.

Full Changelog: v1.5.2...v1.6.0

v1.5.2

• fix: set the cwd to the nearest package.json directory (#32)
• fix: make sure to gracefully close the socket (#35)
• fix: test specification using default node:test import (#42)
• fix: not resolving variables in 'nodejs-testing.extensions' config (#46)
• fix: changes to extensions config not updating if folders change
• fix: stack trace pointing to the wrong location with certain libraries (#50)

Full Changelog: v1.5.1...v1.5.2

v1.5.1

• Add Node 22 support. This also fixes an issue where tests aside from those intended to run were executed.
   
  Full Changelog: v1.5.0...v1.5.1

v1.5.0

What's Changed

• feat: add test coverage support

Full Changelog: v1.4.0...v1.5.0

Note: this requires VS Code 1.88, which is not yet released to stable and is presently only on Insiders.

v1.4.0

What's Changed

• feat: enable running a pretest command via a nodejs-testing.pretest setting
• feat: allow customizing the test file pattern via the nodejs-testing.extensions.filePatterns setting
• fix: report syntax errors / require failure better
• feat: add envFile support for test runner via nodejs-testing.envFile / nodejs-testing.env settings
• feat: use pretty-format when formatting objects in expected/actual diffs
• feat: add a new nodejs-testing.style for prettier display of test output
• feat: add a new nodejs-testing.verbose for diagnostic output when running tests
• fix: test cases sometimes not reporting results
• fix: support template literals in require
• refactor: update dependencies, drop TAP

New Contributors

• @uwinkelvos made their first contribution in #30

Full Changelog: v1.3.2...v1.4.0

v1.0.2

• fix: test parsing failing on arg-less call expression (#3)

v1.0.1

• fix: report failing location as first non-internal position
• fix: files not found causing tests to not be reported (#2)
• fix: runner not working with .mjs files (#1)