coverband: Controller file being unexpectedly ignored
We have one particular controller file that is not showing up in our coverband reports and we’re trying to figure out why.
I’ve looked at this, but it doesn’t offer any clues:
> Coverband.configuration.ignore
=> [".erb$", ".slim$", "/tmp", "vendor/ruby-*"]
The controller in question is app/controllers/users/registrations_controller.rb and coverage data for it IS generated locally, but not in production. And we know that it’s used in production and handling traffic.
We also have a file at app/controllers/registrations_controller.rb. (Yeah, I know, don’t ask…) Is it possible that there’s a name collision of some sort?
Any suggestions for how to debug this since it’s only happening in prod?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (8 by maintainers)
I fell behind on various things and forgot to ever write up the debugging flow, to understand
Coveragevscoverbandand how to gather additional details in dev. I assigned this to myself and will try to get back to it.If anyone figured out their production issues please let me know.
I ran into a similar issue but almost all of my code outside of
production.rbwas being ignored and it turned out to be this configuration option: https://docs.scoutapm.com/#autoinstruments, which rewrites some code, thus preventingCoveragefrom working.This specific problem felt like an issue with the scout library so I filed an issue there: https://github.com/scoutapp/scout_apm_ruby/issues/343