v4.0.0-alpha.3 (Jan 27, 2021)

Summary

4th alpha release of v4 (#576). This release mainly contains the following changes:

• Added full support for parameterized tests across the extension. (#649)
  • support all variations of the .each syntax for both test and describe blocks.
  • The parameterized tests get aggregated status indicator
  • The extension can now report/highlight multiple errors for a given test block. All errors from parameterized tests are shown inline, via hovering message, and in the PROBLEM panel.
  • The extension's debug codeLens can now select from multiple candidates for a given test block. Therefore, each parameterized test can be debugged with a selected set of parameters.
• Optimization: no longer needs to stop/start jest process when debugging. (#649)
• start to migrate to the new jest.jestCommandLine setting and deprecate jest.pathToJest and jest.pathToConfig. (#644)
• Enhance README for rootPath setting. (#643)

Detail see CHANGELOG

Migration Notes

There is a known issue in jest that parameterized tests have incorrect locations (jestjs/jest#10412). The fix (jestjs/jest#10413) was merged in jest-26.5.0. Therefore, the minimal jest version for projects with parameterized tests should be >= 26.5.0

Contributors 🙏

@johnnyreilly, @connectdotz

How to test

you can manually install the plugin by downloading the vscode-jest-4.0.0-alpha.3.vsix below, then follow the vscode instruction: install from vsix. You can always revert to the official version if needed: install-previous-versions.

There is a lot of new stuff, so we added quite a few debugging messaging to help diagnose problems. if anything didn't do what you expected, please turn on the debug mode and file issues.

v4.0.0-alpha.2 (Dec 20, 2020)

Summary

3rd alpha release of v4 (#576). This release mainly contains the following changes:

• when debugging tests, the extension is now aware of their containing describe-blocks so it can distinguish tests with the same name but in different describe blocks. (#632)
• coverage formatter enhancement: added color customization; fixed coverage formatter parsing error and inconsistency; improved coverage help in README etc (#635)
• update vulnerable dependencies

Detail see CHANGELOG

Contributors 🙏

@connectdotz

How to test

you can manually install the plugin by downloading the vscode-jest-4.0.0-alpha.2.vsix below, then follow the vscode instruction: install from vsix. You can always revert to the official version if needed: install-previous-versions.

There is a lot of new stuff, so we added quite a few debugging messaging to help diagnose problems. if anything didn't do what you expected, please turn on the debug mode and file issues.

v4.0.0-alpha.1 (Aug 17, 2020)

Summary

Second alpha release of v4 (#576). This release contains the following changes:

• move test status decoration to the gutter so it won't interfere with code formating. (#599)
• enhance debug config to be more compatible with the workspace settings. (#567)

Detail see CHANGELOG

Contributors 🙏

@glentakahashi, @Tymek

How to test

you can manually install the plugin by downloading the vscode-jest-4.0.0-alpha.1.vsix below, then follow the vscode instruction: install from vsix. You can always revert to the official version if needed: install-previous-versions.

There is a lot of new stuff, so we added quite a few debugging messaging to help diagnose problems. if anything didn't do what you expected, please turn on the debug mode and file issues.

v4.0.0-alpha.0 (July 1, 2020)

Summary

This is the first release of v4 (#576). This release contains the following features:

• a brand new test result matching algorithm that aims to address all "unknown" test status indicator issues, such as duplicate test names or by using jest.each.

• fixed coverage merge issue that made coverage overlay unreliable sometimes.

• improve create-react-app and --watchAll detection logic.

• upgrade dependencies to the current version and resolved all known security vulnerabilities.

• many other development tooling changes as well, such as migrating to eslint.

Contributors 🙏

@stephtr, @lordofthelake, @connectdotz

How to test

you can manually install the plugin by downloading the vscode-jest-4.0.0-alpha.0.vsix below, then follow the vscode instruction: install from vsix. You can always revert to the official version if needed: install-previous-versions.

There is a lot of new stuff, so we added quite a few debugging messaging to help diagnose problems. if anything didn't do what you expected, please turn on the debug mode and file issues.

v3.2.0 (Apr 27, 2020)

Bug Fix

• fix orphan process leak for some user environments, such as react.

Enhancement

• multi-root environment will now report error with the workspace folder name.
• some minor document and message fixes.

Contributors 🙏

@stephtr, @berniedurfee, @raphaelbs, @connectdotz

---

CHANGELOG | commit history

v3.1.1 (Jan 15, 2020)

Minor release

Bug Fix

• fix -reporters loading failed with whitespace in its path.

---

CHANGELOG | commit history

v3.1.0 (Dec 20, 2019)

In this release, we improved accessibility, UI, code coverage, error display and addressed a few frequently reported bugs.

New & Improved

• improve accessibility:
  • replaced the test status indicators from color-differentiated circles to status specific icons
• status bar improvement:
  • more accurately reporting testing running/stopping via jest reporters
  • adopted vscode native spinner
  • will show coverage and watch modes
• improve test error messages:
  • when hovering over test errors, the error message will no longer be arbitrarily truncated.
  • color escape sequences should be gone from all error messages.
• improve test coverage: now coverage can be truly dynamically turn on/off without any customization
• fix space or special characters in path failure bug: the execution commands are now in quotes and executed via shell

For complete list, see Changelog.

Config Change

• code coverage:
  • If you have hardcoded --coverage or --watchAll in your jest command/config for showing code coverage, it is no longer needed. If you want to see code coverage always, just set "jest.showCoverageOnLoad" to true in vscode settings; otherwise it is probably more efficient to toggle on code coverage only when needed.
• jest.enableInlineErrorMessages
  • the default value has changed to false in this release to favor the more completed error message when hovering-over. If you prefer to see inline errors, set this flag to true in vscode settings.

Contributors

There are quite a few changes accumulated since the last release. It's exciting to see help from so many different contributors: @rhalaly, @shruda, @rfgamaral, @jmarceli, @garyking, @vuchl, @tarepan, @connectdotz, @stephtr

Thank you 🙏

v3.0.2

merged from beta releases (3.0.0-pre, 3.0.1-pre), recap:

What is new

One of the main features introduced in 3.0.0 is to support vscode multi-root workspaces, a popular request, especially for monrepo projects.

This release also included many other highly desired features/fixes, such as

• debugger break-point misalignment
• restart commands
• snapshot preview
• test result being ignored (not updating test status indicator)
• improve template-literal test name support

and some internal improvement:

• reduced the extension footprint by 90% (installation/upgrade should be a lot faster)
• applied security patches flagged by github
• added linter for more consistent coding style

see #442 and Changelog for more detail.

Many thanks 🙏 to @escaton, @blikblum, @vdh, @qalex, @connectdotz, @stephtr !

v3.0.1-pre

What is new

• introduced webpack for packaging the extension, which cut the package size from 40M to 4M!
• addressed security vulnerability for dependencies flagged by GitHub

Thanks, @stephtr !

(See more change detail for 3.0.0)

How to run with this pre-release?

1. download vscode-jest-3.0.1.vsix below
2. install the plugin: code --install-extension vscode-jest-3.0.1.vsix
   • this should install the extension to your vscode extensions folder.
3. restart vscode
   • You can then go to the extension tab in vscode and find Jest extension, if it shows "3.0.1" then the installation succeeded.

v3.0.0-pre

What is new

One of the main features introduced in 3.0.0 is to support vscode multi-root workspaces, a popular request, especially for monrepo projects.

This release also included many other highly desired features/fixes, such as debugger break-point misalignment, restart commands, snapshot preview, etc, please see Changelog for detail.

Many thanks 🙏 to @escaton, @blikblum, @vdh, @qalex!

pre-release

The muti-root change is not trivial, it impacted every component as they all need to be workspace/folder aware now. Thus we created this pre-release for people to play around and help us identify issues sooner. We encourage all users to try 3.0.0 pre-release when possible. (You can always switch back to the official version 2.9.2 if needed).

feel free to file issues or come to discuss with us in #442

How to test with 3.0.0?

1. download vscode-jest-3.0.0.vsix from here
2. install the plugin: code --install-extension vscode-jest-3.0.0.vsix
   • this should install the extension to your vscode extensions folder.
3. restart vscode
   • You can then go to the extension tab in vscode and find Jest extension, if it shows "3.0.0" then the installation succeeded.