My project at https://github.com/jhsu802701/losemoneyfast is rated at
98.7%
test coverage. I’m getting dinged for
config/initializers/rack_profiler.rb
.
Is there something I can do to fix this or to get the CodeClimate engine
to
skip this file in its test coverage analysis?
It’s easier to see changes when I’m at 100%. What I’m trying to do is
analogous to configuring Rubocop and Rails Best Practices to ignore
certain
violations. (Given how nitpicky these tools can be, some violations may
not be worth correcting.)
On Sat, Mar 26, 2016 at 11:11 PM, Jason H., Ruby on High Speed Rails <
[email protected]> wrote:
My project at https://github.com/jhsu802701/losemoneyfast is rated at
98.7% test coverage. I’m getting dinged
for config/initializers/rack_profiler.rb .
Is there something I can do to fix this or to get the CodeClimate engine
to skip this file in its test coverage analysis?
You’ve just slipped off the edge of using metrics to meaningfully
improve
your testing to gaming the metric collection to meaninglessly improve a
metric.