test(population-density-data): add GEOHASHLIST support and rework time/error model#128
Open
albertoramosmonagas wants to merge 4 commits into
Open
Conversation
albertoramosmonagas
requested review from
jgarciahospital,
maheshc01 and
sachinvodafone
as code owners
Contributor
Author
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
1 participant
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.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This PR updates the ATP test feature file for retrievePopulationDensity to align with the next meta-release's schema and operational model. Scenario count grows from 22 to 41.
Key changes: fields renamed from startDate/endDate to startTime/endTime throughout; added full test coverage for a new GEOHASHLIST area type (alongside the existing POLYGON), including its specific success and error scenarios; reworked the async flow (sinkCredentials → sinkCredential, new operationId tracking, new failure-callback scenario) and split error codes between 400 (request validation) and 422 (semantic/processing errors); added missing 403 and 429 error scenarios; and added several generic-validation error cases (malformed body, unexpected properties, invalid x-correlator).
Scenario tags were restructured to group errors by HTTP status (400.01, 401.01, 422.01, etc.) instead of a flat sequential index, and a handful of longstanding typos were fixed (boundry→boundary, recieved→received).
Net effect: moves from a polygon-only, date-based, single-error-tier model to a dual-area-type, date-time-based model with status-segmented error handling and a fully specified async failure path.
Which issue(s) this PR fixes:
Fixes #109
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.