Websites change and template exports

Verification Boundary

The suite invokes production lifecycle services or persistence against its test database. Each fixture and directly called participant belongs to the repository named in the register; this is a local integration boundary.

What This Suite Proves

Change and template exports is the inspected subject. The file contains executable engineering checks in the registered lifecycle scope. Those checks have no acceptance binding here; registration preserves their existence without assigning unsupported scenario coverage.

What It Does Not Prove

Source inspection supplies no passing run. The suite does not establish console behavior, deployment configuration, complete removal in every application or recovery from a provider failure beyond its declared seams. A local zero inventory covers declared and seeded resources only.

Real Dependencies and Test Doubles

The suite exercises production export readers and record mapping against its fixtures. Where it records staged parts, the source supplies the staging or file sink through a test seam; recorded output does not prove object-store credentials, multipart recovery or package delivery.

Must Not Be Doubled

Keep the production service or persistence function and the database constraints, row policies and guarded removal functions under test real. For dispatcher cases, keep route selection and authorization real as well. Provider and remote-application seams must remain explicit and cannot stand in for deployed cross-application qualification.