DOT-5874: Refactor PDF result fetching and enhance error handling for project ID #354
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.
This pull request updates the PDF results polling and processing logic to align with a new API response format and improves the reliability and clarity of PDF test result reporting. The main changes involve updating field names to match the new API, ensuring required identifiers are present, and improving the structure of result handling.
API Integration and Data Structure Updates:
fetchPdfResults
method inhttpClient
to use the new endpoint (/smartui/2.0/build/screenshots
), requireproject_id
andbuild_id
in request parameters, and handle missingprojectId
with an explicit error.projectId
to theBuild
interface and ensured it is set after PDF upload, so subsequent API calls have the required context. [1] [2]Field Name and Data Mapping Adjustments:
screenshotName
→screenshot_name
,mismatchPercentage
→mismatch_percentage
, etc.) throughout the polling and grouping utilities to match the new API response structure. [1] [2] [3] [4] [5]Polling Logic and Output Improvements: