Does coverband ignore downstream call stack if a path is ignored in config.ignore?

[harshanails]

Just wondering if a bunch of cron workers are added to the ignore list, does the called substack/classes also be added to the ignore list or will they still show up in the runtime coverage?

More context here

@danmayer

[danmayer]

I believe this is just pretty naive regex ignoring so the underlying call stack and other code would still show up in the runtime coverage.

if everything is in a common subdirectory, you can pass regex to ignore an entire folder path... If you are trying to do something specific you can let me know and I can perhaps help, but the ignoring is a pretty simple filter layer to not store the data to redis or display it if it is already in redis.

[harshanails]

If you are trying to do something specific you can let me know and I can perhaps help

@danmayer Yes, I am trying to see if any code path which matches a cron_worker and the classes loaded by these cron_workers can be excluded from being reported to ::Coverband.configuration.store.coverage(::Coverband::RUNTIME_TYPE)

[danmayer]

Ok, so I had an idea that might work for this... You can disable coverband on various processes. So if you have a cron job process, you could just disable coverband, and the job and all the code it loads / runs will then be excluded. You can disable it for the process by setting the COVERBAND_DISABLE_AUTO_START environment variable.

for example:
COVERBAND_DISABLE_AUTO_START=true bundle exec bin/cron_worker --job JobName