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

Improve error message about unrealistic result #1417

Open
hugo-vrijswijk opened this issue Sep 15, 2023 · 0 comments
Open

Improve error message about unrealistic result #1417

hugo-vrijswijk opened this issue Sep 15, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers hacktoberfest Great issues to pick up for Hacktoberfest

Comments

@hugo-vrijswijk
Copy link
Member

hugo-vrijswijk commented Sep 15, 2023

If Stryker4s exits too fast, all mutations are survived/killed or maybe some other condition happens, there could be more informative logging.

Example of logging now:

[info] 574 mutant(s) detected as having no code coverage. They will be skipped and marked as NoCoverage
[info] Mutation run finished! Took 23 milliseconds
[info] Total mutants: 574, detected: 0, undetected: 0
[info] Mutation score: n/a%
[info] Written HTML report to /stryker4sdir/target/stryker4s-report/1694730938007/index.html
[success] Total time: 5 s, completed Sep 14, 2023, 4:35:38 PM

We could suggest some possible reasons, debug options (like enabling test-runner stdout) and solutions the user could try to hopefully get Stryker4s working

@hugo-vrijswijk hugo-vrijswijk added enhancement New feature or request good first issue Good for newcomers hacktoberfest Great issues to pick up for Hacktoberfest labels Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers hacktoberfest Great issues to pick up for Hacktoberfest
Projects
None yet
Development

No branches or pull requests

1 participant