---
title: "Verify report date filters use the selected timezone"
description: "Test a sandbox date-range report with events near midnight, comparing included identifiers and aggregate totals against an independent timezone fixture."
canonical_url: "https://vostride.com/agent-library/reporting-exports/report-timezone-date-boundary.md"
md_url: "https://vostride.com/agent-library/reporting-exports/report-timezone-date-boundary.md"
content_kind: "recipe"
topic: "reporting-exports"
---

# Verify report date filters use the selected timezone

Test a sandbox date-range report with events near midnight, comparing included identifiers and aggregate totals against an independent timezone fixture.

## Risk

A report can display a local date range but filter UTC timestamps, dropping or including boundary events incorrectly. Place controls on both sides of the intended boundary and inspect the exact exported identifier set.

## Fixtures

- An owned sandbox event report with synthetic events immediately before, at, and after the selected local-day boundaries.
- A report timezone setting and an independent fixture manifest mapping each canonical timestamp to its expected local day.
- A read-only event oracle and artifact parser with exact expected included identifiers and aggregate values.

## Steps

1. Select the prepared local date range and report timezone, then verify both settings are visible in the report summary.
2. Inspect the on-screen matching records and verify the start-boundary event is included while the preceding event is excluded.
3. Export the report and verify the job retains the same date range and timezone metadata.
4. Parse the artifact and compare all boundary identifiers and totals with the independent manifest, including the documented treatment of the range end.

## Expected results

- Included events follow the selected timezone and documented boundary inclusivity.
- On-screen and exported record sets agree with the independent timestamp mapping.
- Aggregate totals reconcile exactly with the included synthetic events.

## False-pass traps

- Noon-only fixtures can pass under both UTC and local filtering.
- A correct total can hide swapping equal-valued events across a boundary.

## Cleanup

- Delete the report artifact and restore the report timezone and date-filter preferences.

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