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
are you able to run jest test from the command line? yes
how do you run your tests from the command line? (for example: npm run test or node_modules/.bin/jest) npx jest --forceExit
Steps to Reproduce
Relevant Debug Info
Expected Behavior
there is a jest test report,i can see the word "branch not covered" by mouse over the yellow highlight block.
Actual Behavior
there is a vscode-jest coverage status,I can't get the nocovered type from the status.
The fastest (and the most fun) way to resolve the issue is to submit a pull-request yourself. If you are interested, feel free to check out the contribution guide, we look forward to seeing your PR...
The text was updated successfully, but these errors were encountered:
@Mrsnoozlebergs you are right that we currently did not expose/differentiate types of branch-not-covered state (such as if-else) in color nor hovering message. This is a good feature to add.
Environment
vscode-jest version
: v4.2.1node -v
: v14.17.5npm -v
oryarn --version
: 6.14.14npm ls jest
ornpm ls react-scripts
(if you haven’t ejected): [email protected]"watch": true,
"onStartup": ["all-tests"]
}
Prerequisite
npm run test
ornode_modules/.bin/jest
) npx jest --forceExitSteps to Reproduce
Relevant Debug Info
Expected Behavior
there is a jest test report,i can see the word "branch not covered" by mouse over the yellow highlight block.
Actual Behavior
there is a vscode-jest coverage status,I can't get the nocovered type from the status.
The fastest (and the most fun) way to resolve the issue is to submit a pull-request yourself. If you are interested, feel free to check out the contribution guide, we look forward to seeing your PR...
The text was updated successfully, but these errors were encountered: