Open MilesCranmer opened 6 months ago
Hmm I'll have to look into it once the nightly issues are resolved, one thought though is that follow-exec doesn't work necessarily properly on llvm coverage depending on your tests the profraw files may be written after your test asserts the command works properly (depending on the method of the assert). So the arg --post-test-delay
was designed to make it work by adding a fudge factor delay after the main test process exits to collect all the profraws
Thanks, I tried --post-test-delay=10
but still at 0% unfortunately.
Hey,
Awesome package, I really appreciate your work maintaining this!
I'm trying to debug why tarpaulin isn't picking up my binary tests for my rust project rip2: https://github.com/MilesCranmer/rip2. I have started using
assert_cmd
to test the CLI functionality but it doesn't seem to get picked up by tarpaulin at all.I have been running tarpaulin with the following options:
I have an integration test here that uses assert_cmd to call the
rip
binary with different options.However, these don't seem to be picked up. I've read through the solutions on https://github.com/xd009642/tarpaulin/issues/903 but they didn't seem to help me. Here is the current output:
^ Oddly you can see that despite all the
test_cli
tests being run, where this line is used to get the binary for the package, the coverage doesn't get picked up. The main tests that should trigger this behavior aretest_cli::*
in the integration tests.(If I turn on the other tests which directly call the library functions, the coverage does work. It's just the binary/CLI components I'm struggling with).
The solutions on https://github.com/xd009642/tarpaulin/issues/903 didn't seem to help me sadly. If there are any other CLI flags I can try, please let me know.
Can reproduce this with:
^ Which will show the 0%.
Cheers, Miles