You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stryker-net does not have runtime errors and as such will never have data for runtime errors. This column is useless for stryker-net users. I also think that columns that are all 0s are not that useful in general. The table is not that easy to read because there are so many columns. Removing columns that are unused would help with readability. We could either hide all 0'd columns by default or we should have a way to specify which columns to display. I think this has to be schema information because otherwise the stryker dashboard would have different columns from a local report.
The text was updated successfully, but these errors were encountered:
Yeah, I definitely see your point. 3 solutions here:
Add something like "reportAppearance" to the schema. I don't like this solution personally.
We could add it as an attribute: "mutant-states": "Killed, Survived", but that means indeed that the HTML report would look different on the dashboard.
This could be solved by allowing mutation testing frameworks to add an appearance section to the json, which would not be part of the schema.
We could decide to remove columns that have only 0s in the entire report.
Stryker-net does not have runtime errors and as such will never have data for runtime errors. This column is useless for stryker-net users. I also think that columns that are all 0s are not that useful in general. The table is not that easy to read because there are so many columns. Removing columns that are unused would help with readability. We could either hide all 0'd columns by default or we should have a way to specify which columns to display. I think this has to be schema information because otherwise the stryker dashboard would have different columns from a local report.
The text was updated successfully, but these errors were encountered: