You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2024. It is now read-only.
Hi there,
first of all, thanks for making such a great integration with the VSCode test explorer. I have a project workspace set up, which contains one Go project, and two typescript/javascript projects that use Jest for testing. For the Go part, the test explorer works fine, but the jest test suites keep rerunning right after they complete, as if stuck in an endless loop. You can see a test run finishes successfully, because I briefly see the test summary at the bottom of the runner output in the console, but after a second or so, the whole suite starts running again, while nothing changes on disk. Because of this, the status of the tests in the test explorer UI are always the 'blue play button'. It never shows if a test fails or succeeds.
Did I configure anything wrong that causes this behavior? I have autorun disabled. Can it be because I am using this extension in a workspace?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there,
first of all, thanks for making such a great integration with the VSCode test explorer. I have a project workspace set up, which contains one Go project, and two typescript/javascript projects that use Jest for testing. For the Go part, the test explorer works fine, but the jest test suites keep rerunning right after they complete, as if stuck in an endless loop. You can see a test run finishes successfully, because I briefly see the test summary at the bottom of the runner output in the console, but after a second or so, the whole suite starts running again, while nothing changes on disk. Because of this, the status of the tests in the test explorer UI are always the 'blue play button'. It never shows if a test fails or succeeds.
Did I configure anything wrong that causes this behavior? I have autorun disabled. Can it be because I am using this extension in a workspace?
Beta Was this translation helpful? Give feedback.
All reactions