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

Clarity about clearing coverband trackers and/or cache. #578

Open
michaeldeitcher opened this issue Feb 10, 2025 · 0 comments
Open

Clarity about clearing coverband trackers and/or cache. #578

michaeldeitcher opened this issue Feb 10, 2025 · 0 comments

Comments

@michaeldeitcher
Copy link

Coverband has been a very useful tool for me. I am currently removing dead code on a project in which I recently disabled the use of a specific feature. Once deployed, I'd like to verify that specific code is no longer being executed.

I'd like to verify the runtime usage of code after the time of deployment. It does not seem that the reports can be scoped by the date of deploy. It looks like the only method to do this would be to clear cache and/or trackers.

Some questions about clearing coverband data:

  • What's the difference between clearing trackers and clearing coverage?
  • What are the risks to running rake coverband:clear ? How dangerous is doing this?
  • Is there a way set config.web_enable_clear so only individual files can be clear not all of the project? Since clearing all coverband data is seen as being a dangerous operation.
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

1 participant