Problem Statement
Currently when a test fails the output already appends the OTEL Body, but there is no good way of viewing the exception, this is the current output
but the error message itself is not always helpful by itself.
NOTE: Is this specific case I'm using TUnit integration of ReqNRoll, the WatchResourceLogs does not work, also tried multiple custom solutions to get the logs out without success, so this simple addition would already solve the problem of helping identity why my tests started failing in the pipeline
Proposed Solution
When available, also print the exception
Alternatives Considered
No response
Feature Category
Test Output / Reporting
How important is this feature to you?
Important - significantly impacts my workflow
Additional Context
No response
Contribution
Problem Statement
Currently when a test fails the output already appends the OTEL Body, but there is no good way of viewing the exception, this is the current output
but the error message itself is not always helpful by itself.
NOTE: Is this specific case I'm using TUnit integration of ReqNRoll, the
WatchResourceLogsdoes not work, also tried multiple custom solutions to get the logs out without success, so this simple addition would already solve the problem of helping identity why my tests started failing in the pipelineProposed Solution
When available, also print the exception
Alternatives Considered
No response
Feature Category
Test Output / Reporting
How important is this feature to you?
Important - significantly impacts my workflow
Additional Context
No response
Contribution