CypressError: Timed out retrying: Expected to find element with selector when date‑picker fails due to locale mismatch

Direct answers

1. Cypress does not ship a per‑test timezone API; the proposed Cypress.config('timezone') is not merged and there is no confirmation it will be added.

2. cy.clock() freezes the timestamp returned by Date.now() but does not change the browser’s timezone offset. To get consistent rendering, freeze the instant with cy.clock() and then generate the expected UI string using a date library (Luxon, date‑fns) with the explicit zone you want the app to use. Assert against that library‑derived string instead of relying on the host zone.

3. For reliable CI date‑picker tests: force a deterministic browser locale, decouple selectors from locale‑dependent text, and control the instant under test. Run CI with a fixed TZ environment variable (e.g., TZ=UTC) and verify the picker renders via data attributes or zone‑aware strings.

Confirmed facts vs likely explanation

Confirmed facts. Cypress executes tests in the host machine’s system timezone. cy.clock() freezes the current timestamp but does not modify the browser’s timezone offset. No per‑test timezone configuration exists in released Cypress.

Likely explanation for the timeout. The selector you use is probably tied to visible, locale‑formatted date text (e.g., MM/DD/YYYY vs DD/MM/YYYY or month names). When the CI host zone or browser locale differs from development, the picker renders a different string or different DOM structure, so the selector is not found and Cypress retries until timeout.

Steps needed for this case

1. Make the instant deterministic.

cy.clock(new Date('2026-01-15T12:00:00Z').getTime(), ['Date'])

2. Generate expected strings with an explicit zone, not the host zone.

// example with Luxon
const { DateTime } = require('luxon')
const expected = DateTime.fromJSDate(new Date()).setZone('America/New_York').toFormat('MM/dd/yyyy')

Use the same explicit zone for both the app under test and the assertion if the app is zone‑aware.

3. Force browser locale for Chrome in cypress.config.js.

e2e: {
  setupNodeEvents(on, config) {
    on('before:browser:launch', (browser, launchOptions) => {
      if (browser.name === 'chrome') {
        launchOptions.args.push('--lang=en-US')
      }
      return launchOptions
    })
    return config
  }
}

Note: browser flags are engine‑specific and may not apply to Firefox.

4. Decouple selectors from formatted text.
• Prefer data attributes like data-testid="date-cell" data-date="2026-01-15" over visible text.
• If the picker must be driven by text, build the selector from the library‑derived string above.
5. CI environment control.
• Set TZ=UTC on the CI runner for reproducibility.
• Run a quick check on a runner with a different zone to confirm the picker still resolves via data attributes.

Verification

• Check cypress.config.js for browser args and locale overrides.
• Inspect the DOM on failure to confirm whether the selector is missing due to a format change.
• Confirm cy.clock is restored after the test.

One missing diagnostic that changes the recommendation: is the failing selector based on visible formatted date text or on a stable data attribute / value? If it is text‑based, the data‑attribute strategy above is required; if it is already stable, the issue is more likely instant/zone drift.