-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0/0 tests passed #749
Comments
this is a known issue and vscode team is aware and hopefully will be addressed soon: microsoft/vscode#129444 (comment)
During the run, only the file level item and above will be marked busy (spinning), we didn't force every item under it to be spinning as well. However, I can see it could be easily missed especially if there are lots of tests in the file... We could experiment with a deep status update... |
Should this be working now? I can see that the vscode ticket is closed, but I also see the "0/0 tests passed" in VSCode 1.60.2 and vscode-jest 4.1.2. |
@dominic-simplan the status on top of the TestExplorer is showing the "latest" run stats, it is not accumulated of the overall tests stats. I can see why it is confusing... Basically, if you are in "watch" mode (the default) and there is no change (determined by jest watchman), then the run stats will show "0/0 tests passed". It should show different stats once you changed something... I agree it will be nice to show the accumulated overall stats, but that was not the case currently. However, you can easily see the "failed" test by either filtering by "Show Only Failed Tests" or change the sort order to "Sort By Status" in the TestExplorer. |
I see, thanks for the explanation! |
as explained above, this is not an issue. |
Environment
vscode-jest version
: v4.1.0-rc.2node -v
: v14.7.0npm -v
oryarn --version
: 6.14.7npm ls jest
ornpm ls react-scripts
(if you haven’t ejected): react-scripts@4.0.3Prerequisite
npm run test
ornode_modules/.bin/jest
) yesSteps to Reproduce
open a repository with tests, focus on text explorer view, wait for tests to run
Expected Behavior
The message at the top reflects the number of passed tests and the total
Actual Behavior
Regardless of how many tests were run and how many did pass, the indicator shows "0/0 tests passed (0.00%)".
If some tests were skipped, this is reported correctly in the sidebar title. The test explorer shows correctly the status of passed/not passed/skipped tests once they are completed (but they are not updated while running, only after the run)
The text was updated successfully, but these errors were encountered: