---
title: "Check inclusive date filter boundaries"
description: "Verify the exact start and end boundaries of a date filter using fixed records on either side of the selected reporting interval."
canonical_url: "https://vostride.com/agent-library/search-filtering/date-range-boundaries.md"
md_url: "https://vostride.com/agent-library/search-filtering/date-range-boundaries.md"
content_kind: "recipe"
topic: "search-filtering"
---

# Check inclusive date filter boundaries

Verify the exact start and end boundaries of a date filter using fixed records on either side of the selected reporting interval.

## Risk

Date pickers often show a correct human range while timestamp conversion excludes the final day or imports records from the previous day. Define the reporting timezone before writing the expected set.

## Fixtures

- A test report uses UTC dates and contains records at June 1 00:00, June 30 23:59, May 31 23:59, and July 1 00:00.
- The application contract states that selecting June 1 through June 30 includes both complete calendar days.
- A seed manifest maps each boundary timestamp to a unique visible record label and identifier.

## Steps

1. Open the report and verify its displayed timezone is UTC, or verify UTC is the configured report fixture timezone.
2. Select June 1 as the start and June 30 as the end, then apply the range.
3. Verify the June 1 and June 30 fixture labels are present and the May 31 and July 1 labels are absent.
4. Move only the end date to June 29 and verify the June 30 record disappears while the June 1 record remains.
5. Restore the full June range and verify the two-record result and visible range label agree.

## Expected results

- The inclusive June range yields exactly the two keys recorded within its UTC boundary interval.
- Changing the end date affects the end-boundary record independently of the start-boundary record.
- The range label persists after application and matches the values used by the fixture oracle.

## False-pass traps

- A count of two could represent the wrong two records; assert identities as well as the count.
- Relative dates such as this month make the fixture drift and can hide timezone defects.

## Cleanup

- Remove the four date-boundary fixtures and clear the report range 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 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)

- [Search and filtering QA recipes](/agent-library/search-filtering.md)
- [Software factory QA library](/agent-library.md)