---
id: TST-PFM-QRY-334
title: Platform report exports
kind: integration
product_area: platform
module: queries
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464
repository: services-platform
files:
  - modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js
implements:
  - ATS-PFM-QRY-013-01
  - ATS-PFM-QRY-013-02
  - ATS-PFM-QRY-013-03
  - ATS-PFM-QRY-013-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: 'The suite’s database fixtures, controlled execution contexts and file-owned external dependency seams.'
evidence:
  - 'services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js'
assertion_bindings:
  - scenario: ATS-PFM-QRY-013-01
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#answers
        a colleague who may not see the private report 404, writing nothing
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#refuses
        a caller without platform.reports.use 403, writing nothing
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#answers
        the report from another tenant’s path 404: it is not that tenant’s
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
  - scenario: ATS-PFM-QRY-013-02
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#accepts
        an Excel export of a table report
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#refuses
        an Excel export of an AG Studio layout at format, writing nothing
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#refuses
        an Excel export of a dashboard, writing nothing
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#refuses
        a CSV, a query’s format, writing nothing
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-013-03
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#refuses
        the renderer’s own parameter name at parameters, writing nothing
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#refuses
        a value that is an object, writing nothing
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#keeps
        a value exactly as sent, untrimmed
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-013-08
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js#names
        the file for the report and the tenant’s date, as a PDF
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
fixture_seams:
  - >-
    services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js:106
  - >-
    services-platform:modules/queries/tests/integration/services/rendering/report-exports.integration.spec.js:97
---

# Platform report exports

## Verification Boundary

The file invokes its service or persistence boundary against local integration fixtures.

## What This Suite Proves

Its assertions check report exports. The assertion bindings identify the corresponding acceptance examples and retain their original test-title citations.

## What It Does Not Prove

Local execution does not establish deployed queue scheduling, every external provider response or a passing result at the pinned revision.

## Real Dependencies and Test Doubles

The integration fixture and any imported dependency seams define the environment. Database-oriented checks use PostgreSQL; file-owned transport, clock, provider or worker seams isolate the explicitly controlled boundary.

## Must Not Be Doubled

Keep the service or persistence operation whose behavior is asserted real. Database constraints and transactions cannot be replaced by fixture answers when they are the subject of the check.