avoid adding null comment in json reporter #16
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.
org.testng.ITestResult#getThrowable
sometimes can havedetailMessage=null
, and this results injson-report.json
having"comment":null
and later a rejection from API when importing results via '/api/v2/import/execution' (Xray Cloud).TestNG test example that generates detailMessage=null:
This PR adds an extra
detailMessage != null
check to favoid adding null comment.