Hi Its not a known issue but also not something we want to support or spend time on. Its intended for normal regular tests, but maybe more broadly just to get a sense of what is covered. It is not really intended for specialized tests like parameterized that can spew many combinations.
On Thu, Jul 24, 2025 at 8:34 PM Mark Webb <elihusma...@gmail.com> wrote: > I've found that when I run the camel-report maven plugin against my code > and check the unit test coverage, I am getting inaccurate results for my > unit tests that are annotated with the ParameterizedTest annotation. Is > this a known issue and/or is there a workaround for this so that I can get > accurate results? > > From what I can tell, the route coverage for the last parameterized test > run is what is reported. I would expect the code coverage to reflect all > of the parameterized tests. > > Thank you, > Mark > -- Claus Ibsen
