Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code coverage at the package level w/ sub-packages merged #265

Closed
sakethram18 opened this issue Oct 26, 2022 · 4 comments
Closed

Code coverage at the package level w/ sub-packages merged #265

sakethram18 opened this issue Oct 26, 2022 · 4 comments
Assignees
Labels
Question Support request issue type S: waiting for clarification Status: additional information required to proceed

Comments

@sakethram18
Copy link

Hello Kover team, I was wondering if there is a way to get the code coverage of a package at the root level meaning the classes included in that package and all the sub-packages included in it. Currently it gives a single list of all packages with parent packages and child packages as siblings. For eg:

Current state:
A.B
A.B.C
A.B.D
A.E

Required state:
A.B (this should contain coverage for direct classes and for packages A.B.C and A.B.D)
A.E

@sakethram18 sakethram18 added Question Support request issue type S: untriaged Status: issue reported but unprocessed labels Oct 26, 2022
@shanshin
Copy link
Collaborator

Hi,
may you clarify, do you describe a situation when packages are displayed in a single list in an HTML report?

eg
image

@shanshin shanshin added S: waiting for clarification Status: additional information required to proceed and removed S: untriaged Status: issue reported but unprocessed labels Oct 26, 2022
@sakethram18
Copy link
Author

@shanshin Yes that is correct. I'm looking to see if there is a way to publish the report such that org.jetbrains line item includes all the subpackages (org.jetbrains.bar).

@shanshin
Copy link
Collaborator

shanshin commented Nov 1, 2022

Unfortunately, at the moment this feature is not implemented.
We will add it when improving the report generator.

@shanshin
Copy link
Collaborator

shanshin commented Nov 1, 2022

Duplicates #272

@shanshin shanshin closed this as completed Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Support request issue type S: waiting for clarification Status: additional information required to proceed
Projects
None yet
Development

No branches or pull requests

2 participants