Skip to content
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

how to distinguish the type of vscode-jest coverage status #835

Open
Mrsnoozlebergs opened this issue Feb 10, 2022 · 2 comments
Open

how to distinguish the type of vscode-jest coverage status #835

Mrsnoozlebergs opened this issue Feb 10, 2022 · 2 comments

Comments

@Mrsnoozlebergs
Copy link

Environment

  1. vscode-jest version: v4.2.1
  2. node -v: v14.17.5
  3. npm -v or yarn --version: 6.14.14
  4. npm ls jest or npm ls react-scripts (if you haven’t ejected): [email protected]
  5. your vscode-jest settings if customized:
    • jest.jestCommandLine? npx jest --forceExit
    • jest.autoRun? {
      "watch": true,
      "onStartup": ["all-tests"]
      }
    • anything else that you think might be relevant? [fill]
  6. Operating system: Linux n248-189-027 4.19.117.bsk.6-amd64 Support showing status bar, and in the problems section #4.19.117.bsk.6 SMP Debian 4.19.117.bsk.6 Mon Jan 4 07:25:51 UTC x86_64 GNU/Linux

Prerequisite

  • 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

image
there is a jest test report,i can see the word "branch not covered" by mouse over the yellow highlight block.

Actual Behavior

image
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...

@Mrsnoozlebergs
Copy link
Author

@connectdotz I've been stuck with this problem for two weeks, can you please give me some advice on this issue

@connectdotz
Copy link
Collaborator

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants