---
title: "Verify an export job and its prepared artifact evidence"
description: "Test export request status and artifact identity while using a separate approved verifier for file contents that screenshots cannot inspect."
canonical_url: "https://vostride.com/agent-library/files-media/export-job-evidence.md"
md_url: "https://vostride.com/agent-library/files-media/export-job-evidence.md"
content_kind: "recipe"
topic: "files-media"
---

# Verify an export job and its prepared artifact evidence

Test export request status and artifact identity while using a separate approved verifier for file contents that screenshots cannot inspect.

## Risk

An export success indicator does not prove the generated file contains the requested records. Keep UI job checks and external artifact verification explicit instead of assuming generic download introspection.

## Fixtures

- A test report contains exactly three known rows with unique keys and synthetic values.
- The product supports a CSV export job, and an approved fixture verifier can retrieve its artifact through the application test interface.
- The expected header names and ordered row keys are recorded before exporting; no customer data enters the artifact.

## Steps

1. Open the test report and verify its three fixture rows and current filter context.
2. Request the CSV export through the UI and verify a new job appears with the intended report name.
3. Wait for the job to reach its completed state and verify a download or artifact action is available.
4. Capture the visible job identifier and invoke the prepared external verifier for that specific job.
5. Verify the independent report confirms the expected headers and three exact row keys, then reopen export history and verify the completed job retains the same identifier.

## Expected results

- The completed UI job belongs to the requested report and current fixture context.
- The external verifier confirms the actual CSV content matches the predetermined header and row oracle.
- The artifact is associated with the newly created job, not an older export with a similar filename.

## False-pass traps

- A clickable Download label proves neither artifact bytes nor row correctness.
- Reading table rows in the browser cannot substitute for verifying the generated export artifact.

## Cleanup

- Delete the test export job and artifact through approved fixture cleanup.
- Remove the three report fixtures when no longer needed.

## 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 test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Files and media QA recipes](/agent-library/files-media.md)
- [Software factory QA library](/agent-library.md)