feat: add status field to JSON report#2700
Merged
eddycharly merged 2 commits intoMay 4, 2026
Merged
Conversation
- Added Status field to OperationReport, StepReport, and TestReport - Added TestReport.Failed() method to rollup failure status - Fixed cross-platform path separator issue in report tests Signed-off-by: Ayush Patel <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2700 +/- ##
==========================================
+ Coverage 66.96% 67.08% +0.11%
==========================================
Files 149 149
Lines 5703 5723 +20
==========================================
+ Hits 3819 3839 +20
Misses 1624 1624
Partials 260 260 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
eddycharly
enabled auto-merge (squash)
May 4, 2026 09:26
eddycharly
approved these changes
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Explanation
When exporting results to JSON, Chainsaw previously omitted the final outcome (pass/fail/skipped) for tests, steps, and operations. This PR adds an explicit
statusfield at all levels of the JSON report, allowing users and external tools to determine test outcomes directly from the JSON without needing to cross-reference JUnit XML or parse error messages.Related issue
Fixes #2503
Proposed Changes
statusstring field toOperationReport,StepReport, andTestReportin the JSON output.TestReport.Failed()to roll up failure status from underlying steps and operations.report_test.gowhere hardcoded forward slashes caused test failures on Windows.Checklist
Further Comments
The
Skippedboolean was removed from the JSON struct in favor of the unifiedstatusfield to keep the output clean and avoid redundancy. All existing report tests have been verified to pass on both Windows and Linux.