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

Per-test coverage report? #314

Open
cbrunnkvist opened this issue Sep 30, 2020 · 2 comments
Open

Per-test coverage report? #314

cbrunnkvist opened this issue Sep 30, 2020 · 2 comments

Comments

@cbrunnkvist
Copy link

cbrunnkvist commented Sep 30, 2020

Is there a way to correlate the name of tests to different files / section of the coverage report? Or vice-versa.

I'm doing some test analysis automation and even a "tests-to-source-files-covered" map would be of great value. As of now, if I have a change to source file F, I have no way of knowing which test classes are relevant to this file, even less so to which lines of that file.

@cbrunnkvist
Copy link
Author

We can see an example of something similar used in the context of mutation testing.

(n.b. JS in the linked example - but the same principle)

@ckipp01
Copy link
Member

ckipp01 commented May 7, 2021

This should be somewhat possible. We just merged in #297 which will include test names which would then be able to be grouped and mapped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants