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

Code Coverage Reporting & UI #973

Closed
ntotten opened this issue Sep 7, 2018 · 2 comments
Closed

Code Coverage Reporting & UI #973

ntotten opened this issue Sep 7, 2018 · 2 comments

Comments

@ntotten
Copy link
Contributor

ntotten commented Sep 7, 2018

It would be helpful to developers if they could see test coverage reports and have UI helpers to determine which parts of their code is tested.

A new command SFDX: Show Test Coverage could be added that did the following:

  1. Ran a test coverage report and showed the results in the terminal
  2. Added coverage indicators in the editor gutter as shown below for the C# example.

image

@ntotten ntotten transferred this issue from forcedotcom/salesforcedx-vscode Jan 28, 2019
@ntotten ntotten transferred this issue from another repository Jan 28, 2019
@ntotten ntotten added this to the Backlog milestone Jan 28, 2019
@mnunezdm
Copy link

Hi,

I didn't know if should open a new Issue or posting in this one.

After last update Code Coverage shows correctly on Apex Classes, but an annoying notification appears every time a class with no code coverage is opened

This happens with Test Classes, maybe it could be great to ignore this files that does not require any line to test

testCodeCoverage

Also, the org selector is now "Lightning" Fast

@ntotten
Copy link
Contributor Author

ntotten commented Mar 21, 2019

This feature shipped two weeks ago.

@ntotten ntotten closed this as completed Mar 21, 2019
@ntotten ntotten modified the milestones: Backlog, Spring 19 Mar 21, 2019
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