The combined examples change a source, its audience or its retained state before checking the dependent outcome. Unbound examples remain proposed, and the coverage finding retains design obligations that these examples do not establish.
The source revisions pin the inspected assertions. A test binding identifies written assertions, and does not establish a successful run or approval of the expected behavior.
Coverage
Rulecovered
Transitionnot-applicable
Validationcovered
Permissioncovered
Edgegap: FND-PFM-QRY-057
Failuregap: FND-PFM-QRY-057
Boundarycovered
Concurrencygap: FND-PFM-QRY-057
Invariantcovered
Interactioncovered
Test Scenarios
13 scenarios proving CAP-PFM-QRY-007; 11 bound to an existing test.
Two users share one role and a saved personal-task question with a requested date.
Steps
Run the shared question as each user with the same date, then remove one user’s dataset grant and rerun.
Expected
Each successful answer contains that runner’s tasks; the revoked runner receives no result.
Data
Use an isolated workspace with the described source records, access grants and a surviving control workspace.
Source
services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#answers not found for a role the caller does not hold, and excludes the record from the list [E2E-SQ-09],services-platform:modules/queries/tests/e2e/saved-queries.e2e.spec.js#refuses to run it for a caller who may not query the dataset as 403, however it was shared
13Finding a report does not grant joined datainteractionapinegativeproposed