Iwo Pieniak

Hi @SimonKagstrom , I really appreciate your work with kcov! I have started using it recently and has proven to be a great tool for Bash testing coverage combined with...

hi @SimonKagstrom , I have been encountering issues when trying to run kcov(v38) with bats(v1.3.0) with GNU bash, version 5.0.18(1)-release (x86_64-apple-darwin19.5.0). The command I am trying to run is: `...

Hi everyone. I am currently trying to run kcov v38 with BATS 1.3.0 with a following command kcov --bash-dont-parse-binary-dir --include-pattern=.sh/ --exclude-pattern=lib/bats coverage \ lib/bats-core/bin/bats tests/monitor.pipeline.bats What I get is: kcov:...

@smatberg-gpe I believe, you need to escape white space in your Unix path. To make your life easier, I would recommend using underscores in the file names.

@smatberg-gpe here’s a stack overflow thread to give you an example - https://stackoverflow.com/questions/19858176/how-do-i-escape-spaces-in-path-for-scp-copy-in-linux Simply speaking, in shell scripting, when you have special characters (in your case spaces) you need to...

Hi @mgonzalezporta, > Is it possible to obtain a code coverage report for Nextflow scripts using nf-test? If not, would you have any alternative suggestions? 1. Are you interested in...

After some deeper thinking, me, @aaron-fishman-achillestx and @byb121 came to a conclusion that implementing a code coverage tool should involve discussion on the paradigm and level of coverage measurement first....

That would be fantastic feature! +1