- prevent auto starting watch-mode jest process when the parent process is stopped, which can lead to orphan process during deactivation among others. - @connectdotz
- adding workspace folder in error message for multii-root projects. - @connectdotz
- fix reporter failed to load due to whitespace in path - connectdotz
- fix test breakage with 'jest-editor-support' internal modules due to automock. - connectdotz
- replacing the status bar spinner with the VS Code spinner - rhalaly
- Fix regex to detect the pluralized message 'snapshots failed' and show the 'Would you like to update your Snapshots' dialog - shruda
- Add 'hair space' (U+200A) after decoration text - @rfgamaral
- Fix decoration color for 'unknown' tests - @rfgamaral
- Improve global and local detection for Jest executable on
win32
platform - @rfgamaral - Set
"extensionKind": "workspace"
inpackage.json
to support remote developement - @rfgamaral - Fix remove ANSI characters from test messages - @jmarceli
- Adjust test result indicators for colorblind people - @jmarceli
- Use short message instead of terse message in test diagnostic tooltip and tab - @jmarceli
- quoting default "pathToJest" to preserve special characters, if any. - @connectdotz
- Fix for when
branch.end.column
isnull
. @garyking - Fix several jest coverage issues and improve usability. - @connectdotz
- Add "Running tests" message to the StatusBar - @jmarceli
- Disable inline error messages by default - @jmarceli
- Fix StatusBarItem when starting Jest without active text editor but only one workspace folder - @stephtr
-
use webpack for compilation, resulting in a much smaller extension size - stephtr
-
fix security vulnerability for dependencies flagged by github - stephtr
-
Support multi-root workspaces - escaton
- multiroot workspace statusBar displays both active folder and workspace summary info - connectdotz
- fix race condition in multi-root projects - connectdotz
- add folder status bar support for multi-root projects - connectdotz
-
support template-literal-string test names by matching with location info from jest result - connectdotz
-
paying down some tech debt, see PR#447 for detail.
-
Add disableOptimisticBPs option to debug configuration. Fixes #400 - blikblum
-
Adds "Jest: Restart Runner" command - vdh
-
replaced deprecated vscode.previewHtml command with webview - qalex
- Prevent ANSI escape codes from appearing in test messages - seanpoulter
- Adds a setting to control when the debug CodeLens appears - seanpoulter
- Support the "Jest: Start/Stop" and "Show output" commands without an active text editor - seanpoulter
- Restart Jest with --watchAll when --watch is not supported without git/hg
- seanpoulter
- Highlight error of failed test when assertion was made outside of test
- Fix regression in handling workspaces that have been bootstrapped with create-react-app - seanpoulter
- Run Jest on Windows in a shell when gathering settings, such that we don't have to deal with the .cmd extension anymore - stephtr
- upgrade to jest 23.3 - connectdotz
- enhanced error reporting and troubleshooting assistance - connectdotz
- Added a
jest.debugMode
setting for self-diagnosis - expand README Troubleshooting area
- expand issue template to include critical settings as well as debug output
- Added a
- retired jestSettings and version lookup logic - connectdotz
- refactor diagnostics to defer some expensive operations to later when the file becomes active. This is to improve performance and correctness, especially for use cases in #349 or #334 - connectdotz
- Adds a setting to control when the debug CodeLens appears - seanpoulter
- Support the "Jest: Start/Stop" and "Show output" commands without an active text editor - seanpoulter
- Restart Jest with --watchAll when --watch is not supported without git/hg
- seanpoulter
- Fix decorators showing corrupt values when two tests of the same name in one file (e.g. in different describe blocks) exist - ThomasRooney
- Add new coverage formatter named GutterFormatter (can be used by setting jest.coverageFormatter to GutterFormatter instead of DefaultFormatter) - Guymestef
- Add the ability to configure debugging of tests - stephtr, connectdotz
- Fixes debugging of tests on Windows (bug introduced in 2.6.2) - stephtr
- Even better detection logic for projects created by
create-react-app
- stephtr
- Adding
.cmd
inpathToJest
on Windows isn't necessary anymore - stephtr - Update settings at runtime - gcangussu
- Improved detection logic for projects created by
create-react-app
- stephtr - Added
JestProcess
andJestProcessManager
abstractions to simplify Jest process management - marcinczenko
- Strips testNames so they can be used as regex - BLamy
- Show "update snapshots" message when multiple snapshot tests failed - uucue2
- Adds ability to open snapshot file directly from test - bookman25
- Start automatically if jest.config.js or jest.json is in workspace - uucue2
- Use pathToJest setting to properly locate jest's package.json and read the version - uucue2
- Fix missing coverage overlay on Windows - seanpoulter
- Toggle coverage overlay without changing documents - seanpoulter
- Fix dot decoration display on Windows - seanpoulter
- Improve the dot decoration placement as we edit - seanpoulter
- Hide Debug CodeLens for skipped tests - seanpoulter
- Mute output from
console.warn
during tests - seanpoulter
- Improve where the Debug CodeLens is displayed - seanpoulter
- The debugger uses the setting
jest.pathToJest
- seanpoulter
- Detect apps bootstrapped using react-scripts-ts - seanpoulter
- Add option to disable codelens - goncharov
- Allow debugging non-successful tests - CzBuCHi
- Adds an option to not run all tests on launch - seanpoulter
- Never sends VS Code an invalid line number for an unexpected result - connectdotz
- Improvements for Create React Native App - anton-matosov
- Improvements for Create React App - seanpoulter
- Adds an option for
"jest.rootPath"
to let you choose the folder to run jest commands - garyxuehong
- Restart jest up to three times upon unexpected exit - connectdotz
- Fixes for Jest 21 - connectdotz
- Improvements to settings auto-completion - vvo
- Support toggling code coverage - bookman25
- Improve error reporting - bookman25
- Apply prettier to the codebase. - macklinu
- Adds coverage support - bookman25
- Jest related depenendency bumps. Should improve the inline messages and crash less. - orta
- Adds an option to not show errors inline in the editor - orta
- Adds an option to not snapshot update requests - orta
- Show channel command - orta
- Supports TS/TSX/JSX .snaps - orta
- Create React App fixes - orta
- Use "jest-test-typescript-parser" for our TypeScript parser - orta
- Bumps min VS code release - orta
Note: This release consolidates a lot of code with the Jest project, and so if you have a custom testRegex
and use
Jest below v20, chances are the decorators will not show. Everything else should be 👍 - orta
- New fancy spinner when running tests - bookman25
- Improved handling of expired test results - bookman25
- Improved underlining of failing expectations - bookman25
- Whitespace fixes for the error messages next to a fail - orta
- tsx support - orta/bookman25
-
Move all of the Jest specific code into a new repo: jest-editor-support where we can share the code with a nuclide implementation. This brings some changes to the development process (see the README) but should only affect users if we've missed something in moving over.
- orta / bookman25 / cpojer
-
Significant improvements to JavaScript parsers - bookman25
-
Introduction of TypeScript support - bookman25
- Prepare for Jest 18 - orta
- Windows + Create React App improvements - brentatkins
- config file improvements - luizbon
- Warning message copy improvements - orta
- Adds an option that allows you to use an external config json file - luizbon
- More windows improvements - KalleOtt
- Separation of VS Code specific code from the extension by creating a lib directory, in preparation for moving to the Jest repo - jestjs/jest#2183 - orta
- Minor improvements for create-react users - orta
- Support for running Jest even in repos where Jest is not a direct dependency via the command
Start Jest Runner
- you will definitely need to set the per-project.vscode/settings.json
to whatever would normally trigger a jest run - orta
- Use green empty circles for tests assumed to be good - gabro
- More windows improvements - bookman25
- Adds support for running the tests inside
create react
apps - orta
- When a Snapshot test has failed, it offers the chance to update your snapshots - orta
- Adds an error message if you're not using Jest 17 - orta
- Windows support - orta
- Adds syntax highlights for the JSX in
.js.snap
files - orta
import type
now shouldn't cause a parser error, and should be fine in test files - orta- Adds an option to disable the initial loading of the runner on a project - orta
- You can start and stop the jest runner via the command pallette. - orta
- You can define your own path to the Jest test runner - orta
- Not a feature, but the code has been thoroughly commented - orta
- Improvements to parsing passing test files - orta
- Only run JS parser on files that match the Jest tesRegex - orta
- Uses all possible Babylon plugins when parsing a test file, should raise exceptions less - orta
- Removes unused commands - orta
- Starts Jest automatically when you're in a project with Jest installed.
- Show individual fail / passes inline.
- Show fails inside the problem inspector.
- Highlights the errors next to the
expect
functions
- orta
- Show when the tests are running - orta
- Switch to use symbols in the status bar - orta
- All Tests in a file are marked red/green when we know whether the file passed - orta
- When we don't know test state yet, show an empty circle - orta
- Adds statusbar support - orta
- Adds fails to the problems section - orta
- Parses current file for it/test blocks - orta