The optimal flow for Jest based testing in VS Code
MIT License
Bot releases are hidden (Show)
Published by connectdotz about 2 years ago
Full Changelog: https://github.com/jest-community/vscode-jest/compare/v4.6.0...v5.0.0
Release Note: v5.0.0 (pre-release)
Published by connectdotz over 2 years ago
Full Changelog: https://github.com/jest-community/vscode-jest/compare/v4.5.0...v4.6.0
Published by connectdotz over 2 years ago
Full Changelog: https://github.com/jest-community/vscode-jest/compare/v4.4.0...v4.5.0
Published by connectdotz over 2 years ago
jest.config.{mjs|cjs|ts}
by @felipecrs in https://github.com/jest-community/vscode-jest/pull/846
Full Changelog: https://github.com/jest-community/vscode-jest/compare/v4.3.1...v4.4.0
Published by connectdotz almost 3 years ago
vscode-jest-tests.v2
, all existing vscode-jest-tests
config will continue to be supported. (#787)vue
language support (#791)@bhrutledge @jlecordier @JeffEmery @connectdotz
Published by connectdotz almost 3 years ago
vscode-jest-tests.v2
, all existing vscode-jest-tests
config will continue to be supported.@connectdotz
Published by connectdotz about 3 years ago
minor release to fix test file might lose test status indicator upon startup for non-watch mode env (#785)
@connectdotz
Published by connectdotz about 3 years ago
This release mainly enhances TestExplore support and added new settings to help customize shell and node env for jest runner process.
Not-yet-executed tests will have a "runnable" status icon so the test menu is always accessible regardless of autoRun mode. (#773)
"jest.debugCodeLens.showWhenTestStateIn": []
.Two new settings are added to customize jest runner process: (#777)
jest.nodeEnv
: append additional env to the jest runner process.envjest.shell
: allow users to choose which shell to use for jest run instead of the default shell.fixed inline popup started to appear in vscode 1.61 even when showInlineError is false (#773)
Added language support for snapshot files (#779)
updated README and fixed typo (#768, #769)
upgrade internal dependency (#775)
@olejec @roottool @Yash-Singh1 @connectdotz
Published by connectdotz about 3 years ago
Another minor release to remove the release messaging. (#763)
Published by connectdotz about 3 years ago
Published by connectdotz about 3 years ago
This release is mainly to support the newly available official TestExplore via a new set of vscode.tests
api in 1.59 build. This provided a nice test-centric view and a more published UI experience that worked pretty well with the existing engine:
This release is backward compatible, all existing settings (other than deprecation of the jest.enableInlineErrorMessages
) would work as before, with an additional setting jest.testExplorer to fine-tune the test explorer behavior.
More info see v4.1 with Test Explorer
see CHANGELOG for more details.
@tommy @connectdotz
Published by connectdotz over 3 years ago
patch release:
.ts
with "<>" casting no longer cause parse error. (#706)See CHANGELOG for more details.
@connectdotz
Published by connectdotz over 3 years ago
patch 4.0.0 for the following issues:
"Jest: Run Related Tests"
keyboard shortcut to avoid conflict: new keybinding: Ctrl-Alt-t or Ctrl-Option-t (Mac)@Agalin @connectdotz @stephtr
Published by connectdotz over 3 years ago
patch 4.0.0 for the following issues:
@connectdotz (special thanks to @dgoemans @obvioussean @macabeus @stephtr who helped diagnose and test the fix)
Published by connectdotz over 3 years ago
This is the official v4 release (finally! 😄)
There are a lot of changes in this release. We will list the major features/changes below, more detail can be found in CHANGELOG
Jest: Setup Extension
is added."jest.autoEnable"
and "jest. runAllTestsFirst"
. If you have these settings, please consider migrate.jest.pathToJest
+ jest.pathToConfig
, which will be deprecated in the future versions."jest.restartJestOnSnapshotUpdate"
"jest.jestCommandLine"
if you have jest.pathToJest
or jest.pathToConfig
customized."jest.autoRun"
if you have customized "jest.autoEnable"
or "jest. runAllTestsFirst"
@stephtr, @lordofthelake, @connectdotz, @glentakahashi, @Tymek, @johnnyreilly
Published by connectdotz over 3 years ago
This release packed a lot of changes that should complete the main v4 (#576) features we aim to deliver :
jest --watch
. (see how to trigger the test run)Detail see CHANGELOG
jest.autoRun
: while the settings are completely backward compatible, it is recommended to migrate to the new setting and stop using the deprecated ones sooner than later.jest.jestCommandLine
, which replaces jest.pathToJest
, jest.pathToConfig
(v4.0.0-alpha.3)@connectdotz
you can manually install the plugin by downloading the vscode-jest-4.0.0-alpha.5.vsix
below, then follow the vscode instruction: install from vsix. You can always revert to the official version if needed: install-previous-versions.
Due to the scope of the changes, we would really love to have as many people testing it as possible. Please do not hesitate to ask questions or raise issues, we can fast-track them much easier in the alpha stage. You have probably also noticed that we have made significant changes in README, please let us know if you have any suggestion to make it more useful for the community.
Published by connectdotz over 3 years ago
5th alpha release of v4 (#576). This release mainly contains the following changes:
src
- prevent future typing related crash.Detail see CHANGELOG
@connectdotz
you can manually install the plugin by downloading the vscode-jest-4.0.0-alpha.4.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.
Published by connectdotz over 3 years ago
4th alpha release of v4 (#576). This release mainly contains the following changes:
.each
syntax for both test and describe blocks.jest.jestCommandLine
setting and deprecate jest.pathToJest
and jest.pathToConfig
. (#644)rootPath
setting. (#643)Detail see CHANGELOG
There is a known issue in jest that parameterized tests have incorrect locations (facebook/jest#10412). The fix (facebook/jest#10413) was merged in jest-26.5.0. Therefore, the minimal jest version for projects with parameterized tests should be >= 26.5.0
@johnnyreilly, @connectdotz
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.
Published by connectdotz almost 4 years ago
3rd alpha release of v4 (#576). This release mainly contains the following changes:
Detail see CHANGELOG
@connectdotz
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.
Published by connectdotz about 4 years ago
Second alpha release of v4 (#576). This release contains the following changes:
Detail see CHANGELOG
@glentakahashi, @Tymek
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.