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

Refresh code coverage view on new test results #11

Open
michenriksen opened this issue May 14, 2023 · 0 comments
Open

Refresh code coverage view on new test results #11

michenriksen opened this issue May 14, 2023 · 0 comments
Assignees
Labels
priority: medium Will be addressed type: enhancement Improvement/addition to existing functionality
Milestone

Comments

@michenriksen
Copy link
Owner

michenriksen commented May 14, 2023

As a user,
  I want the code coverage view to automatically refresh the current file on new test results
So that, 
  I can quickly see how my changes affect coverage without opening the new coverage view

  • Discussion: Automatically load code coverage overview #9
  • Include an option in the coverage view toolbar or Settings menu to enable or disable automatic refresh. This gives users the understanding that their code coverage updates automatically, and allows them the choice to deactivate this feature if preferred.
  • Show a notification beneath the coverage view toolbar, indicating when the code coverage was last updated. This assures users that their data is current.
@michenriksen michenriksen converted this from a draft issue May 14, 2023
@michenriksen michenriksen self-assigned this May 14, 2023
@michenriksen michenriksen added this to the v.1.0.0 milestone May 14, 2023
@michenriksen michenriksen added priority: medium Will be addressed type: enhancement Improvement/addition to existing functionality labels May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium Will be addressed type: enhancement Improvement/addition to existing functionality
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant