Check whether the outcome improved
Exercise supported date representations
Import known dates using supported explicit formats and serial values only where documented. Include examples that expose day/month order and relevant date-system boundaries. Record intended values independently and compare exact calendar results, rather than accepting any plausible date or copying the parser’s output into the expected fixture.
Check confirmed format and rejection
Where users select a date format or source convention, verify that choice survives preview and execution. Try an unsupported or ambiguous representation and inspect its guidance. The importer should not silently guess a date when its documented contract requires additional context that the file and confirmed settings do not supply.
Inspect subsequent calendar behavior
Reopen saved values and check a representative sort, filter, or scheduled-date display. If timestamps are supported, exercise their timezone path separately from date-only values. Confirm the correction preserves already supported date strings and does not turn a date-only value into a shifted day through an unnecessary time conversion.
What to carry forward
Accept when the supported representation matrix preserves known calendar meaning and unsupported inputs follow the declared failure behavior. Record producer and timezone cases not exercised. Keep historical reconciliation outside this pass unless original source context establishes each intended date; a correct new conversion does not identify every previously misinterpreted value.
Technical background: Microsoft support.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow