Dan Mayer

icon indicating a website link http://mayerdan.com icon indicating an email [email protected]

icon company @Shopify icon location Denver, CO icon location A distributed team believer, a generalist that works in whatever tools are needed. Expert Rubyist, in other languages it works on my machine.

Results 150 comments of Dan Mayer

Track Gem Support, please bring back

I am closing this as there are a number of reasons tracking gem usage is a different sort of problem than app tracking.

Track Gem Support, please bring back

yeah, it was far to slow to track all gem usage... I think something more targetted that would only track specific gems could help, but I also think many folks...

Summary output for rake coverband:coverage

hey sorry @bessey this just totally got lost in my stack.. but I have added the summary data you would like... Let me know if you want any other calculations...

Summary output for rake coverband:coverage

This will go out in the next release closing.

Adds report-only CSP

hey folks sorry for the delay on this got a bit lost in my queue and we had an alternative solution in our apps so I hadn't needed anything like...

Adds report-only CSP

let me know if this works @jwg2s or @scruti

Adds report-only CSP

full details on the code change https://github.com/danmayer/coverband/pull/470

Track a (shared) gem instead of the app itself

I am closing this as there are a number of reasons tracking gem usage is a different sort of problem than app tracking.

Generating a static HTML snapshot/report of coverage after having run coverband in production for a period

OK, finally going to get back to this one and close it out. @FlorianASchroeder thanks for the tip, I basically copied your method for the JSON report and added it...

auto_instruments breaks coverage

My understanding is the way that auto instrument rewrites code isn't compatible with the Ruby standard lib Coverage approach... So Coverband which relies on standard lib coverage isn't compatible with...