You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have many levels of scripting on top actual test binary.
And a test binary is executed with different options by the scripts
If I can only include test process by name then I do not have to change any existing scripting for generating coverage. Otherwise I would have to handle merging of coverage reports my self.
I used --include-path but this is causing slowdown.
Thank you.
The text was updated successfully, but these errors were encountered:
Sorry, I wasn't clear.
I was running my scripts through kcov.
I just read another ticket #177 so it might not be possible to get coverage of my tests as my top level scripts are in bash and python.
My command looks something like below kcov ./run_my_tests.sh
and the shell script runs python script.
Aha, yes, I'm afraid that isn't possible at the moment. I'm not quite sure how to implement it either, so for now I'm not investigating it further. The difficult thing is to determine what are actual Python scripts from bash (and the other way around!).
Closing as a duplicate to #177, reopen if this isn't the case.
I have many levels of scripting on top actual test binary.
And a test binary is executed with different options by the scripts
If I can only include test process by name then I do not have to change any existing scripting for generating coverage. Otherwise I would have to handle merging of coverage reports my self.
I used
--include-path
but this is causing slowdown.Thank you.
The text was updated successfully, but these errors were encountered: