You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if the files list is huge, then the PR comment generated will also be huge,
the paths input takes multiple reports, but we don't have wildcard support for this input Wildcard in report paths? #20 ,
What is considered as a module?
If we have only one coverage.xml file referred in paths, then treat each <group> (if it exists) in the report as a module. If there are no <group>s, then treat it as a single module project.
If the paths contains multiple coverage.xml file, then treat each report as a module.
If the paths contains multiple coverage.xml file, and each report in turn contains <group>, then treat the report as a module. Either flat out the <group> or treat each <group> as a sub-module.
Things to do:
Add capability to segregate coverage info module wise
Add rendering capability to create the comment with coverage for modules
Show coverage for full project
Breakdown coverage module wise
Show coverage for files under each module. Have this collapsed by default and users can expand if wanted.
The text was updated successfully, but these errors were encountered:
For multi-module project we can have two cases:
For both the cases, the jacoco-report action works, but it could be made better:
paths
input takes multiple reports, but we don't have wildcard support for this input Wildcard in report paths? #20 ,What is considered as a module?
paths
, then treat each<group>
(if it exists) in the report as a module. If there are no<group>
s, then treat it as a single module project.paths
contains multiple coverage.xml file, then treat each report as a module.paths
contains multiple coverage.xml file, and each report in turn contains<group>
, then treat the report as a module. Either flat out the<group>
or treat each<group>
as a sub-module.Things to do:
The text was updated successfully, but these errors were encountered: