Include errors from failing tests in coverage report

[lldata]

When a test fails, it is currently impossible to see from the html report, what went wrong.

I would be really nice for developer experience, if it was possible to see the assertion / exception, that caused the test to fail.

For assertions that fail on an assumption that the flow should be in a specific place, it would be extra nice, if you could where the assumption was.

[martinschimak]

That's a really nice idea. Probably with some implications we have to think about - in particular how assertion exceptions could be augmented in order to inform a visualisation library like this one. Could you eventually point to an example or add some more information how exactly you are testing your process models and which libraries you are using for this?

[StephenOTT]

bump from the work related to: #32:
Here is the errors output from the Spock usage:

Example where the wrong Task was in a wait state. The specific line number from the source test is also added (pulled from the stacktrace). So you can reference the errors in the html report, and it also tracks back to the specific Spec and feature down to the specific assertion line number.

Each error is its own code block