Hello Marc,
First, I want to apology for a delay of my response. I started discussion about how to detect test duplication by using of JaCoCo. Maybe I didn’t describe this functionality well. The goal is to extend coverage report by source calls. I see there two major benefits. With this new functionality we will be able to know from where was covered code called (from which tests) and we could find duplicated test scenarios easier, it can be used for pruning duplicate tests and by that, decreasing test execution time of any project using JaCoCo. I prepared a simple demo of how to get source code call in JaCoCo run. https://github.com/jakubschwan/jacoco-demo I know that this new feature changes JaCoCo functionality and it should be by default not activated. So this new functionality will be added as extension of JaCoCo and can be turned on and off by a system property. That means that by default JaCoCo will have the same behaviour as before. Next steps 1. I will start working on changes in API based on the demo and implementing the functionality afterwards. To avoid introducing new bugs, every pull request will contain tests. 2. As this enhancement, when turned on, may have impact on performance, I will provide performance comparison of JaCoCo runtime before changes, after changes and after changes with functionality turn on. Do you agree with this plan? If you have any concerns please let me know. Best regards Jakub Schwan -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/6268ff13-bea4-4b82-9388-8c48eb972509%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
