Issues
- 0
- 3
[BUG] vscode-jest-tests.v2 Debug Configuration does not replace variables when restarting session
#1148 opened by tim-helloquickly - 6
"Click to run tests" doesn't work on Jest v30
#1109 opened by h-yon - 1
[BUG] Entire testing file triggered prior rather than individual test when running tests using it.each(...)
#1144 opened by YasiTL - 3
[FEATURE] Single test result output
#1149 opened by akrolasik-bc - 1
Search for "jest" in the Test Explorer matches every test
#1150 opened by dinofx - 3
Different jest.jestCommandLine settings for run vs debug
#1081 opened by nbolton - 6
[FEATURE] Run Tests button still visible in folded-code
#1139 opened by walston - 2
[FEATURE] Option to completely disable terminal
#1143 opened by asportnoy - 1
[BUG] Editor continues to show test failure icon after test run is passing
#1145 opened by mysticflute - 2
Jest times out during debug with fake timers
#1085 opened by romulof - 3
[BUG] "Play" icons move after running test suite
#1142 opened by mortske - 1
[BUG] test result size wired on start
#1133 opened by yoyoys - 7
[BUG] The plugin opens multiple terminals on startup
#1140 opened by akrolasik-bc - 5
[BUG] Cannot debug on VSCode 1.88
#1136 opened by lamuertepeluda - 8
[BUG] This project cannot be used
#1137 opened by crazyair - 7
[BUG] Not able to run test more than once
#1124 opened by hkan0157 - 1
[FEATURE] Support for native vscode coverage API
#1135 opened by romap0 - 2
- 1
[BUG]the version on open-vsx.org is outdated (5.2.3)
#1130 opened by DetachHead - 3
- 4
- 2
[BUG] Extension v6.2.2 does not activate
#1121 opened by MorMundHS-MA - 3
[BUG] "testing.openTesting": "openOnTestFailure" opens the Test Results viewlet every test suite run, instead of only on failures
#1118 opened by GeorgeWL - 3
Where did the autoRevealOutput option go?
#1115 opened by pmcelhaney - 10
"Test Results" panel aggressively steals focus
#1111 opened by andrewheumann - 1
Test result is revealed automatically on each save
#1113 opened by javierfmarq - 1
[BUG] Jest extension TESTS RESULTS console output causes VS Code to steal focus
#1117 opened by rcbevans - 7
Extension is unable to locate tests because path segments are omitted from --testPathPattern
#1112 opened by yegorpetrov - 3
Test Results output is empty
#1094 opened by Godrules500 - 2
jest.nodeEnv does not expand variables
#1095 opened by esmiralha - 18
No tests are detected
#1086 opened by flixman - 2
Bypass jest command check for non-jest projects
#1107 opened by tbsuht - 1
node env is not take into debug mode
#1106 opened by sebbi08 - 4
Debug mode doesn't work - Extension adds a prefix and an invalid path to jest command line
#1101 opened by marviobezerra - 2
"Cannot read properties of undefined (reading 'uri')" when attempting to view code coverage
#1103 opened by sohmc - 3
- 7
Running tests from whole folder does not work, wrong testPathPattern option
#1079 opened by akwodkiewicz - 3
Error loading new preview extension
#1099 opened by jpierson-at-riis - 0
Show tests that fail to run as failed
#1098 opened by ocie - 1
Unable to run tests in .github/actions on Windows
#1096 opened by nbolton - 2
How to keep message in `test results`
#1090 opened by fly50789 - 1
Single test regex semantic error (maybe)
#1084 opened by dbwodlf3 - 3
tests with parenthesis or other special characters, don't match on individual execution
#1083 opened by olafbuitelaar - 6
Extension as dependency
#1082 opened by MKdir98 - 1
Unable to ReRun last test
#1076 opened by Kikketer - 1
- 2
- 1
Error: Invalid testPattern
#1072 opened by TheNotary - 1
On Win10 Extraneous Backslashes are Present in Filenames When using "Run Test".
#1070 opened by ScottSEA