-
Notifications
You must be signed in to change notification settings - Fork 113
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 and align html-output #272
Comments
I personally don't use the html report and don't really see the point of it. But I am open to PRs to improve it for those who do find it useful. |
In case any mutmut user is interested in improving the html reporting capabilities, I would like to gently plug https://github.com/stryker-mutator/mutation-testing-elements which we created as a generic mutation testing report including a json schema, with the intent that we could hopefully standardize mutation testing output across tools. An example of what it looks like here: https://dashboard.stryker-mutator.io/reports/github.com/stryker-mutator/robo-coasters-example/master#mutant |
Nice. That seems much more sane to support than maintaining a reporting infrastructure in mutmut itself! |
For my own future reference: |
I like MutMut; it has become a default tool in in my toolset. However, ...
The result is sometimes a bit hard to grasp. This while the html-report (index.html) is a very-simple table (and file does not comply to the current HTML-standard)
When doing a big project, we got a long list (table) in no particular order. So it hard to find the part (eg dir) to focus on. Nor is is conviniant to find the worst files
My request is to improve this, and align it to e.g coverage, another tool in my toolbox.
Although it's another tool, they are comparable in use and reporting. For example
coverage html
also gives a table with measurements pro file. See this Example ReportProbably (read: hopefully) one can reuse a lot of that code.
Thanks
The text was updated successfully, but these errors were encountered: