🚀 Feature Request: Support for Multiple `runId`s in Azure DevOps Test Results API

[abhiskuma77]

Context

Currently, the Azure DevOps REST API endpoint for listing test results (GET /test/Runs/{runId}/results) only supports querying results for a single runId at a time. This limitation poses significant challenges when working with multiple test runs, especially in large-scale CI/CD pipelines.

Problem

To fetch results for multiple runs, we must loop through each runId and make individual API calls. This approach:

• Increases latency due to sequential or parallel requests.
• Risks hitting API throttling limits, especially in high-volume environments.
• Adds unnecessary complexity to client-side logic.

Proposed Solution

Introduce support for batch querying by allowing multiple runIds to be passed as a query parameter (e.g., runIds=123,456,789). This would:

• Reduce the number of API calls.
• Improve performance and scalability.
• Simplify integration for developers and DevOps teams.

Alternatives Considered

• Parallel requests: Reduces latency but still counts toward rate limits.
• Filtering via Runs - Query API: Helps identify relevant runs but doesn’t solve the result-fetching bottleneck.

Request

Please consider adding support for multiple runIds in the test results API or provide an alternative endpoint that allows bulk fetching of test results.