---
title: "Verify localized ambiguous dates save the intended day"
description: "Check a localized date field using an ambiguous day and month, confirming its saved calendar date and downstream display without timezone drift."
canonical_url: "https://vostride.com/agent-library/localization/ambiguous-date-entry.md"
md_url: "https://vostride.com/agent-library/localization/ambiguous-date-entry.md"
content_kind: "recipe"
topic: "localization"
---

# Verify localized ambiguous dates save the intended day

Check a localized date field using an ambiguous day and month, confirming its saved calendar date and downstream display without timezone drift.

## Risk

A date such as 04/05 can be interpreted two ways and still look valid. Establish the intended calendar date in an independent fixture before entry and compare stored date components, not only a formatted label.

## Fixtures

- An owned sandbox due-date form configured for a documented day-first locale and a disposable task without a due date.
- A fixture requirement selecting 4 May of the test year, with the accepted visible date-entry format recorded explicitly.
- A read-only task endpoint exposing the canonical calendar date and a second product view such as a monthly agenda.

## Steps

1. Open the task editor and verify the locale cue or date-field format is consistent with the prepared day-first setting.
2. Enter the localized representation of 4 May and verify the picker highlights May 4 rather than April 5 before saving.
3. Save and reopen the task; verify its date label still represents May 4 under the selected locale.
4. Open the May agenda and verify the task appears on the fourth; inspect the April fifth cell and verify the task is absent there.
5. Read the independent task oracle and verify the canonical stored date has month 05 and day 04 without an unintended time-of-day conversion.

## Expected results

- The picker, detail view, and agenda resolve the input to May 4.
- The canonical date components remain month 05 and day 04.
- No duplicate or shifted occurrence appears on April 5 or an adjacent day.

## False-pass traps

- An unambiguous date such as 25/05 cannot expose swapped day and month parsing.
- Comparing two labels produced by the same formatter does not establish stored date correctness.

## Cleanup

- Clear the fixture task due date and restore its original locale 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)

- [Localization QA recipes](/agent-library/localization.md)
- [Software factory QA library](/agent-library.md)