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
Rulegap: FND-PFM-QRY-063
Transitioncovered
Validationcovered
Permissioncovered
Edgegap: FND-PFM-QRY-063
Failurecovered
Boundarycovered
Concurrencygap: FND-PFM-QRY-063
Invariantgap: FND-PFM-QRY-063
Interactioncovered
Test Scenarios
15 scenarios proving CAP-PFM-QRY-013; 11 bound to an existing test.
01Export admission checks report authority and audiencepermissionapinegativetest
A dashboard has two widgets and its requester loses one source permission between print-page requests.
Steps
Start rendering, complete a permitted source read, revoke access and let the next source request proceed.
Expected
The later refusal ends the export without a file containing partial data or a refusal message.
Data
Use an isolated workspace with the described source records, access grants and a surviving control workspace.
Source
services-platform:docs/queries/reports.md#6. Dashboards,services-platform:modules/queries/tests/integration/services/rendering/render-report.integration.spec.js#fails the export access_lost rather than printing a page of refusals
14Report files use the shared file-access boundaryinteractionapiproposed