---
title: "Verify long-running exports use a consistent snapshot"
description: "Test a sandbox report export while prepared records change externally, checking that the finished file follows the documented snapshot consistency policy."
canonical_url: "https://vostride.com/agent-library/reporting-exports/export-snapshot-during-edits.md"
md_url: "https://vostride.com/agent-library/reporting-exports/export-snapshot-during-edits.md"
content_kind: "recipe"
topic: "reporting-exports"
---

# Verify long-running exports use a consistent snapshot

Test a sandbox report export while prepared records change externally, checking that the finished file follows the documented snapshot consistency policy.

## Risk

A report assembled in chunks can combine old and new values into a dataset that never existed. Establish the export snapshot policy and distinguish records changed before the snapshot from those changed afterward.

## Fixtures

- An owned sandbox report with a known total and enough synthetic records to span multiple export chunks.
- An external export-worker fixture that pauses after snapshot establishment and applies a recorded update to selected records before continuing.
- A read-only snapshot manifest and artifact parser oracle containing both pre-change and post-change expected values.

## Steps

1. Request the report export and verify the job identifier and initial filter scope are recorded before the worker checkpoint.
2. Confirm the external fixture reports the snapshot established, then applies its prepared updates and releases the worker.
3. Wait for the job to complete and verify the UI identifies the completed export rather than a newly requested replacement job.
4. Parse the retrieved artifact and compare every changed record with the expected snapshot version; verify totals and record count correspond to one coherent snapshot.

## Expected results

- Every exported record follows the documented snapshot boundary consistently.
- Aggregate totals reconcile with the artifact record values from that same snapshot.
- The completed artifact belongs to the original requested export job.

## False-pass traps

- Checking only unchanged records cannot detect mixed-version chunking.
- A report total copied from current live data can mask rows exported from an older snapshot.

## Cleanup

- Delete the report artifact, restore changed fixture records, and disable the worker pause.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)

- [Reporting and export QA recipes](/agent-library/reporting-exports.md)
- [Software factory QA library](/agent-library.md)