rmuir commented on PR #11882: URL: https://github.com/apache/lucene/pull/11882#issuecomment-1295505148
Personally I don't think its confusing with the filter (`--tests`). When writing new functionality/tests, I like to iterate and see what branches etc of the code the new test is covering. jacoco also has plugins for IDEs that make that workflow easy too. My basic assumption is that jacoco agent just makes a bitset with on/off bit corresponding to each bytecode, so you can't see fancy stuff like "how many times this line of app code was hit in tests" or "which tests tested this". Clover did some of that, but with insane resource usage. So for me being able to use it with --tests to see exactly what the specific test(s) covered is really useful, because you don't exactly have an alternate way to see that info with jacoco. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
