ATS-PFM-QRY-010 Review and select records from a list: Capability Test Specification
Markdown Design / Platform / Questions, record exploration and data delivery / Working with record lists / Capability Test Specification Coverage Rule covered Transition gap: FND-PFM-QRY-060 Validation covered Permission covered Edge covered Failure gap: FND-PFM-QRY-060 Boundary covered Concurrency gap: FND-PFM-QRY-060 Invariant covered Interaction covered Test Scenarios 13 scenarios proving CAP-PFM-QRY-010
01 Retained navigation survives local edits invariant api proposed
Proves BR-CAP-PFM-QRY-010-01Preconditions The records being reviewed are already inside one stored navigation window. Steps Move among retained identities after editing a displayed record. Expected The window’s stored order remains; full-result stability beyond renewed reads is not claimed. Data Prepare isolated fixtures for the states described here. Source services-platform:modules/explorer/services/navigation/navigation-sessions.ts :locateInNavigationSession 02 Navigation inputs identify an ordered match validation api negative test
Proves BR-CAP-PFM-QRY-010-02Preconditions An accessible ordered contact list exists. Steps Start without a record, without sorting, with columns and with a nonmatching record. Expected Invalid shapes return 400 and the missing match returns a located conflict. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/explorer/tests/e2e/explorer-navigation-api.e2e.spec.js #refuses a body naming no record as 400 03 Navigation supplies positions without values rule api test
Proves BR-CAP-PFM-QRY-010-03Preconditions A retained session contains twelve identities. Steps Locate the first, middle and final identities. Expected The response includes position, total and existing neighbours without record values. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/explorer/tests/e2e/explorer-navigation-api.e2e.spec.js #answers the record’s position and the total, which is what "2 of 12" is drawn from 05 Return state remains available from retained sessions edge api test
Proves BR-CAP-PFM-QRY-010-05Preconditions A session exists for an owner who later loses dataset access. Steps Locate an outside identity, omit the identity and read retained state after access loss. Expected Position and neighbours can be absent while return state remains; no window renewal is implied. Data Use the existing binding’s controlled fixture data. Bound to Source services-platform:modules/explorer/tests/e2e/explorer-navigation-api.e2e.spec.js #answers no position for a record that is not in the frozen set, rather than refusing 08 Joined navigation uses base-record grain rule api proposed
Proves BR-CAP-PFM-QRY-010-08Preconditions A joined recipe includes contacts with absent employers. Steps Start navigation and obtain its count. Expected Positions and total match the distinct base-record population. Data Prepare isolated fixtures for the states described here. Source services-platform:docs/explorer.md #4. Navigating a result set 11 Record navigation needs complete journey proof interaction browser proposed
Proves AS-JNY-PFM-QRY-003-01Preconditions A twelve-record list is reviewed while records can change. Steps Open the second record, move forward and backward, and edit a retained record. Expected Retained-window order is checked; stability across rebuilt windows remains outside this proposed assertion. Data Prepare isolated fixtures for the states described here. Source services-platform:docs/explorer.md #4. Navigating a result set 13 Renewing navigation checks the view’s data access again interaction api negative proposed
Proves BR-CAP-PFM-QRY-009-07BR-CAP-PFM-QRY-010-05Preconditions A recipe-anchored list has a navigation session and the owner loses base-dataset access. Steps Read a retained identity, then move beyond the retained window and request whole-result selection. Expected Retained return state remains available; renewal and selection fail the current dataset access check. Data Use an isolated workspace with the described source records, access grants and a surviving control workspace. Source services-platform:modules/explorer/tests/e2e/explorer-views-api.e2e.spec.js #refuses a joined recipe to a caller who may not query a dataset it joins to, as 403,services-platform:modules/explorer/services/navigation/navigation-sessions.ts:extendForward ← Previous Capability Test Specification ATS-PFM-QRY-009 · Organize reusable views of record lists: Capability Test Specification Next Capability Test Specification → ATS-PFM-QRY-011 · Maintain a shared report library: Capability Test Specification