Platform data export artifacts.table

Verification Boundary

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

What This Suite Proves

Its assertions check data export artifacts.table. 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.