-
Notifications
You must be signed in to change notification settings - Fork 21
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
Introduce a new key for test framework output displayed in HTML report #1576
Comments
I think we should call it |
Seems fine to me. More important I think is finding a good way to display this. And do we make this a field of mutant, unit test or both? |
Yeah, good questions. I thought it was for mutants only. Probably @maks-rafalko will be able to answer in detail. |
this should definitely be a field of Regarding displaying, it's up to you guys, but what I want to underline is that this output can be quite big, depending on the tests and test runner. For example, for one of the real Mutant and PHPUnit test framework, it can be like this (I've added output as test:
|
by the way, here is a full HTML report generated for Infection itself, probably you will find it helpful during implementation of this feature request (if you decide to add it). This HTML report contains test framework outputs in Unfortunately GitHub does not allow uploading html files, so I've added it to zip archive. |
That's very useful yes! I think the easiest solution might be to put it in the horizontal drawer, as it is designed for a lot of text. |
It should at the very least not open my default. |
We are integrating Stryker's HTML report into @infection, and I would like to discuss a new key for displaying the whole test framework output for a particular Mutant
Current behavior
Currently, there is a
statusReason
key that is created to display only "assertion message", as I was told by @nicojs. However, in order to better understand why particular Mutant was killed or not, it would be nice to have the whole test framework output.Suggested solution
Probably, it would be nice to add a new key like
testFrameworkOutput
/testRunnerOutput
to store it.Please see the current behavior:
and desired behavior:
As you can see on the first screenshot, output from
statusReason
is not formatted, because it is wrapped with<h6>
instead of<pre>
as on the 2nd screenshot.On Infection Playground, we have the same feature to display the whole output which is IMO very useful, see the right of the image:
Alternative solution
Instead of adding a new key,
statusReason
can be used, but<h6>
should be replace with<pre>
to correctly format the message with\n
The text was updated successfully, but these errors were encountered: