Filtering options for coverage analysis · Issue #15 · jacoco/jacoco · GitHub
@t1 Except anylysis of the cases (see wiki) we're not working on this. Also
- @mfriedenhagen created a project to create test classes with different compilers
- @marchof played with bytecode pattern matching
I assume the main work would be to transport the config to the agent
Actually filtering should happen at analysis time. Therefore the agent does not need any parameters for filtering.
From my point of view the main work is to efficiently match bytecode patterns and design an API that allows to hook filters into the analysis process. Any clever idea is welcome here!
Read full article from Filtering options for coverage analysis · Issue #15 · jacoco/jacoco · GitHub
No comments:
Post a Comment