Repository navigation
Support outcome filtering option in test results - #1011
Merged
Manoj Singaperumal (skmanoj) merged 5 commits intoMar 18, 2026
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1011 +/- ##
=======================================
Coverage ? 93.78%
=======================================
Files ? 16
Lines ? 1626
Branches ? 344
=======================================
Hits ? 1525
Misses ? 23
Partials ? 78
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Kathan Sanghavi (KathanS)
approved these changes
Mar 17, 2026
Manoj Singaperumal (skmanoj)
approved these changes
Mar 17, 2026
Zhaoyang Li (lizy14)
approved these changes
Mar 18, 2026
|
nit: update PR title to better reflect the scope of changes. It's not just support output filtering; it also added test case name, error message, stack trace etc. in response |
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
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.
Summary
Returns useful fields from test results, including testCaseTitle, errorMessage, stackTrace.
Adds optional outcomes parameter for server-side filtering (e.g. ["Failed", "Aborted"])
Why switch from getTestResultDetailsForBuild to getTestRuns + getTestResults
The previous API (getTestResultDetailsForBuild) returns lightweight result entries even with shouldIncludeResults=true — they contain only id, outcome, durationInMs, and testCaseReferenceId, but not testCaseTitle, errorMessage, or stackTrace. Its $filter parameter supports OData-style outcome filtering, but the results lack the detail fields that make them actionable.
getTestResults (per run) returns full TestCaseResult objects with all fields populated, and natively supports an outcomes parameter for server-side filtering. This avoids fetching all results when only failed test cases are needed.
GitHub issue number 887 and 985
Before the changes
After the changes - focused only on the failed test by using the filter logic
✅ PR Checklist
🧪 How did you test it?
Local mcp testing
Replace with use cases tested and models used