---
title: "Verify filtered exports include every matching page"
description: "Check a sandbox export from a paginated filtered report, ensuring it contains the complete matching result set and excludes records outside the filter."
canonical_url: "https://vostride.com/agent-library/reporting-exports/filtered-export-full-result-set.md"
md_url: "https://vostride.com/agent-library/reporting-exports/filtered-export-full-result-set.md"
content_kind: "recipe"
topic: "reporting-exports"
---

# Verify filtered exports include every matching page

Check a sandbox export from a paginated filtered report, ensuring it contains the complete matching result set and excludes records outside the filter.

## Risk

An export can accidentally serialize only the visible page or omit the active filter. Use matching records across multiple pages and explicit nonmatching controls, then compare identifier sets rather than only the displayed total.

## Fixtures

- An owned sandbox report with twenty-three matching records across at least three pages and seven nonmatching control records.
- A disposable viewer account and a saved filter combining project and status, with an independent expected identifier manifest.
- An artifact parser oracle and read-only report endpoint that expose the complete fixture dataset independently of pagination UI state.

## Steps

1. Apply the project and status filter and verify the first page and displayed total correspond to the matching fixture set.
2. Navigate to the second page, request export of all filtered results, and verify the export review retains both filter conditions.
3. Retrieve the completed file through the approved workflow and verify its parsed identifier set contains all twenty-three matches.
4. Compare the artifact against the independent manifest and verify no control record, duplicate identifier, or missing earlier-page result; reopen the job and verify its stored filter scope.

## Expected results

- The artifact contains the full filtered result set across every page.
- All seven nonmatching controls are absent from the parsed export.
- The job scope remains tied to both filter conditions rather than the current page cursor.

## False-pass traps

- Matching the visible page row count can falsely validate a page-only export.
- An equal total can conceal one missing match replaced by one out-of-filter record.

## Cleanup

- Remove the export artifact and restore the report filter preference.

## 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)