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

Deep link to specific mutant #2573

Open
CzBuCHi opened this issue Jun 12, 2023 · 6 comments
Open

Deep link to specific mutant #2573

CzBuCHi opened this issue Jun 12, 2023 · 6 comments

Comments

@CzBuCHi
Copy link

CzBuCHi commented Jun 12, 2023

Is your feature request related to a problem? Please describe.
I sometimes get "Mutant 4234 is only covered by failing tests." error message. It would be nice to see what exactly this mutant mutated, so i can determine why tests fails (specially when test do not fail when run outside stryker)

Describe the solution you'd like
Add text input & 'goto' button to html report, where i can write mutant id and report will show me given mutant in code

Describe alternatives you've considered
Currently i can manually look into json report inside html to find mutant change in there ...

Additional context
Ideal view after hitting 'goto' button:
image

@rouke-broersma
Copy link
Member

rouke-broersma commented Jun 12, 2023

"Mutant 4234 is only covered by failing tests." means the unit tests that cover this mutant were failing in the initial testrun in which no mutants are active so the mutation should not be relevant.

Deeplinks to specific mutants sound like a good feature request for the html report.

@rouke-broersma rouke-broersma transferred this issue from stryker-mutator/stryker-net Jun 12, 2023
@rouke-broersma rouke-broersma changed the title Ability to see mutant #4234 Deep link to specific mutant Jun 12, 2023
@dupdob
Copy link
Member

dupdob commented Jun 12, 2023

I think the problem is that mutant ids are no longer visible in report (they used to be), hence making this kind of warning hard to use.
Conversely, it makes difficult to use the log to try to understand the result for any given mutant.
The id should be accessible somewhere; alternatively, the log lines related to this mutant should be accessible.

@rouke-broersma
Copy link
Member

@dupdob agree, will discuss

@CzBuCHi
Copy link
Author

CzBuCHi commented Jun 18, 2023

not sure if it belongs here, but it would be nice to see what mutant caused
"VsTest did not report the end of test session in due time (* ms), it may be frozen."

edit: this should be placed somewhere in summary (otherwise it will be overriden)

@dupdob
Copy link
Member

dupdob commented Jun 18, 2023

this message is .Net specific, so this does not belong here, indeed.
That being said, this message relates to situation where VsTest fails to stop or start, which is a bug, either in Stryker or VsTest. This is different from a regular timeout situation, where Stryker can identify which mutations triggered the timeout.
you can track/discuss in issue 2560 in Stryker.Net for more info (stryker-mutator/stryker-net#2560)

@hugo-vrijswijk
Copy link
Member

hugo-vrijswijk commented Aug 20, 2024

This would be nice for linking to a test from a mutant, but also linking to a mutant when viewing a test.

When going back in history it'd be great if the mutant/test you were viewing were also still open

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

4 participants