Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/jest-community/vscode-jest/issues/894 below:

asyncError not caught causing failing tests to pass · Issue #894 · jest-community/vscode-jest · GitHub

1. vscode-jest version: 4.6.0
2. node -v: 16.16.0
3. npm -v or yarn --version: npm 8.11.0
4. npm ls jest or npm ls react-scripts (if you haven’t ejected): jest@28.1.3
5. your vscode-jest settings if customized:
   • jest.jestCommandLine? npx jest
   • jest.autoRun? false
   • anything else that you think might be relevant? [fill]
6. Operating system: osx 12.5

• are you able to run jest test from the command line? yes (with npx)
• how do you run your tests from the command line? npx jest

https://github.com/marr/jest-async-fail

1. npm install
2. npx jest
3. see failing test
4. open in vs code with extension and run test
5. see passing test

This is blocking us from fully adopting/trusting the plugin at the moment. Some screenshots are included to potentially point out that within the jest runner for this test, asyncError is set to an Error object, but as you can see below things are green in the ide.

Thanks for any help

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4