Skip to main content

Date Functions and Formatting in Scenario Editor

Last reviewed: September 21, 2026

Use this article when Scenario Editor tests need to generate, transform, or validate dates. Make date handling explicit to avoid timezone and locale issues.

  • Define the expected input and output date formats before scripting.
  • Use consistent timezone assumptions across test data and application UI.
  • Avoid hard-coded dates unless validating a fixed historical record.

Validation workflow

  1. Identify whether the value is generated by the test, read from the UI, or returned by an API.
  2. Normalize date strings before comparing values.
  3. Parameterize offsets such as today, tomorrow, or end-of-month.
  4. Validate edge cases around month boundaries, leap years, and daylight-saving changes when relevant.
  5. Log both raw and formatted values when troubleshooting failures.

Note: Use “Scenario Editor” in current documentation instead of older Test Designer naming where the workflow applies to current AIQ.

Last updated: September 21, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Back to top