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.

Sign up for GitHub

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

Jump to bottom

Tracker: Code Coverage #2153

Open
3 tasks
worksofliam opened this issue Jul 9, 2024 · 0 comments
Open
3 tasks

Tracker: Code Coverage #2153

worksofliam opened this issue Jul 9, 2024 · 0 comments
Assignees
@worksofliam
Labels
idea-seperate Best fit into a seperate extension using the extension APIs vscode-api Specific to the VSCode Extension API

Comments

@worksofliam
Copy link
Contributor

worksofliam commented Jul 9, 2024 •
edited
Loading

It's time to release code coverage, but this time using the VS Code testing API instead of a custom view.

VS Code now supports statement coverage, which is exactly what IBM i Code Coverage provides.

  • ability to import zip
  • ability to view zip by file and then statement coverage, including percentage per file
  • consider ways to execute a coverage test from the UI. The only extension allowed the user to define tests in a custom UI. Do we still want this?
@worksofliam worksofliam added the idea Feature suggestion label Jul 9, 2024
@worksofliam worksofliam self-assigned this Jul 9, 2024
@worksofliam worksofliam added idea-seperate Best fit into a seperate extension using the extension APIs vscode-api Specific to the VSCode Extension API and removed idea Feature suggestion labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@worksofliam worksofliam

Labels
idea-seperate Best fit into a seperate extension using the extension APIs vscode-api Specific to the VSCode Extension API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@worksofliam