Handle test failures with no message #3
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/cc @harvesthq/ep and @pusewicz @maria-faulisi @braddunbar who encountered these
In this build (and others) it seems like there's a new type of test failure that produce a junit file a bit different from what we've seen until now. The culprit is this error element that looks like:
The code expected the
message
to always be present, it seems. I've made it fallback to use thetype
when there's nomessage
. This repo is already a fork of the original plugin, because it didn't show things the way we liked (back in the day), I'm not planning to look much further than this :P