The following chapters describe the implementation details: https://www.jacoco.org/jacoco/trunk/doc/implementation.html <https://www.jacoco.org/jacoco/trunk/doc/implementation.html> https://www.jacoco.org/jacoco/trunk/doc/flow.html <https://www.jacoco.org/jacoco/trunk/doc/flow.html>
If you want to go deeper you can explore the source code which is well documented and tested. Regards, -marc > On 27. Oct 2023, at 10:41, 'Bowen (Tony) Sun' via JaCoCo and EclEmma Users > <jacoco@googlegroups.com> wrote: > > OK, thanks! But if I want to know the mechanism how Jacoco generating code > coverage, are there any useful materials? I have read the official > doc(https://www.jacoco.org/jacoco/trunk/doc/counters.html), while there are > little useful information. > > On Friday, October 27, 2023 at 1:50:45 PM UTC+8 Marc Hoffmann wrote: > Hi Yiichan, > > it is hard to tell what causes this in your setup. I would start with > comparing two reports with different coverage figures. Drill-down both > reports and try to find a pattern where coverage changes. It might be caused > by non-deterministic tests or problems with the test setup or execution data > collection. > > Regards, > -marc > > >> On 25. Oct 2023, at 11:23, Yiichan Sun <yiich...@gmail.com >> <applewebdata://2A03DFCA-9639-4240-92E9-E48A8E3BB783>> wrote: >> > >> My team use Jacoco one year ago. We integrated Jacoco with Codecov in Github >> workflow, and set a periodical action to generate code coverage report every >> day. However, the coverage changes dramatically. Even We don't change any >> code, the next day it gives us a changed code coverage. Especially when >> running integration tests. >> >> So I just want to know: >> 1. what makes the code coverage fluctuating so fast, even no more new >> commits? Due to the mechanism of running many tests in concurrency? >> 2. Or something wrong in the aggregation of integration tests report? >> 3. what's the mechanism of the generation of integration test code coverage >> report in Jacoco? >> >> Thanks! >> > >> -- >> 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 jacoco+un...@googlegroups.com >> <applewebdata://2A03DFCA-9639-4240-92E9-E48A8E3BB783>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jacoco/94663a4c-8a4d-4a60-a4d9-f5fe5dfb196fn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jacoco/94663a4c-8a4d-4a60-a4d9-f5fe5dfb196fn%40googlegroups.com?utm_medium=email&utm_source=footer>. > > > -- > 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 jacoco+unsubscr...@googlegroups.com > <mailto:jacoco+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jacoco/dec3faa5-aa6d-4954-8acd-833c8ab659cfn%40googlegroups.com > > <https://groups.google.com/d/msgid/jacoco/dec3faa5-aa6d-4954-8acd-833c8ab659cfn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 jacoco+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/5A35D796-6B7E-41B3-8C89-8D3B78E911CC%40mountainminds.com.
