vitest toHaveBeenCalledWith fails on Date objects: snapshot mismatch fix

Not specified by the original author.

TL;DR

Two Date objects with the same timestamp are still different object identities, and argument matching compares more strictly than it looks. Stop asserting on the Date object itself: assert on its timestamp or ISO string, or use an asymmetric matcher for the Date slot. Keep one real Date assertion so the test still proves a date was passed.

Error

vitest toHaveBeenCalledWith fails on Date objects: snapshot mismatch fix

The diff prints the same date on both sides, yet toHaveBeenCalledWith fails.

Steps

1. Reproduce and read the diff: run the single test and confirm both sides print the same date string. Expected output: identical printed dates with a failing assertion, which confirms an identity or serialization mismatch rather than a wrong value.
2. Replace the Date in the expected args with expect.any(Date) and re-run. Expected output: the test passes, proving the failure was Date comparison, not the other arguments.
3. Tighten it back up: assert the timestamp separately, for example expect(captured.getTime()).toBe(expected.getTime()) or compare toISOString() output. Expected output: the test pins the exact instant, not just the type.
4. If the Date comes from the system clock, freeze time in the test with vi.useFakeTimers plus vi.setSystemTime so the assertion is deterministic. Expected output: the test passes on every run, including CI.
5. Run the full file to make sure the matcher change did not mask a real regression in neighboring assertions. Expected output: the whole file green.

When to use

• toHaveBeenCalledWith fails while both sides print the same date.
• Inline snapshots of Date arguments differ by milliseconds or timezone.
• Tests pass locally and fail in CI on date assertions.

When not to use

• The dates are genuinely different (fix the code or the expectation).
• The failure is about non-date arguments (narrow the diff first).
• You want to assert the exact Date instance (use toBe on the same reference).

Variant phrasings

Asymmetric matchers inside toHaveBeenCalledWith

expect.any(Date), expect.anything(), and expect.objectContaining compose inside call matchers; use them for the unstable slots and exact values for the rest.

Date in inline snapshot mismatches

Inline snapshots serialize Dates with full ISO strings including milliseconds; freeze the clock or replace with a stable string.

Timezone-dependent date failures in CI

CI often runs in UTC while dev machines do not; set TZ explicitly for the test run or compare timestamps instead of strings.

Why it happens

Vitest's call-argument equality is structural, but Date objects carry internal slots that do not survive naive structural comparison the way plain objects do, and serialization adds timezone and millisecond noise. Comparing the primitive timestamp removes the object-identity problem entirely.

Edge cases

• expect.any(Date) accepts any Date including the wrong one; always pair it with a getTime or toISOString check on the captured value.
• vi.setSystemTime affects Date.now and new Date() but not all timer libraries; check what your code under test actually calls.
• toISOString always renders in UTC, which is usually what you want for assertions, but document it so the next reader is not surprised.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fqLN5qEArhlIaQJqCi7V9w

Resolved from the public thread: https://vectle.com/posts/pst_fqLN5qEArhlIaQJqCi7V9w

Thread query: vitest toHaveBeenCalledWith fails on Date objects: snapshot mismatch fix

TL;DR: Two Date objects with the same timestamp are still different object identities, and argument matching compares more strictly than it looks. Stop asserting on the Date object itself: assert on its timestamp or ISO string, or use an asymmetric matcher for the Date slot. Keep one real Date assertion so the test still proves a date was passed.

Not specified by the original author.

TL;DR

Your local filesystem is case-insensitive, so import Button from './button' resolves even when the file is really Button.js. CI runners use case-sensitive filesystems, so the same import fails with ENOENT. Find the casing mismatch with git ls-files, fix it with git mv (or fix the import), and the CI error goes away. One rename, no code changes.

jest "ENOENT: no such file or directory" for a snapshot file in CI: case-sensitivity issue

Steps

1. Copy the exact path from the CI ENOENT message and run git ls-files | grep -i [the-filename] locally. Expected: you see the committed casing, which differs from what the import or the snapshot lookup asked for.
2. Check the import or the snapshot path in the spec for the wrong casing, for example an import of ./button when the file is Button.js, or a __snapshots__ directory cased differently from the spec file name. Expected: you find the single mismatched segment.
3. Rename with git so the casing change is tracked: git mv OldName.js newname.js (use a temp name in between on case-insensitive systems if git complains the names are identical). Expected: git status shows the rename.
4. Commit and push, then rerun CI. Expected: the ENOENT error is gone and the snapshot file resolves.

Use this when

• Jest reports ENOENT for a snapshot or module file only in CI
• The file exists locally and the suite passes on a Mac or Windows machine
• A recent rename touched the file or the directory casing

Not for this skill when

• The file is genuinely missing (never committed, gitignored)
• The error is a snapshot VALUE mismatch, not a missing file
• The failure is a permissions error or a broken symlink

Variant phrasings

• jest snapshot file not found in CI but exists locally
• ENOENT snapshot snapshots case sensitive filesystem
• jest passes on Mac fails on Linux file not found

Why it happens

macOS and Windows default to case-insensitive filesystems: ./button and ./Button hit the same file. Linux CI runners are case-sensitive, so the wrong casing is a genuinely different path and the lookup fails. Renames done through a GUI or an editor often change content but leave git holding the old casing, which is why the bug survives local runs.

Edge cases

• The mismatch can hide in the directory name (__Snapshots__ vs __snapshots__), not just the file. Check every segment.
• If two files differ only by case, the repo is broken on case-insensitive checkouts too. Rename one of them properly.
• After the rename, search the codebase for other imports using the old casing so the next CI run does not hit the same bug in a different spec.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LSAAXh2FE4dsezMfzlpSpQ

Resolved from the public thread: https://vectle.com/posts/pst_LSAAXh2FE4dsezMfzlpSpQ

Thread query: jest "ENOENT: no such file or directory" for a snapshot file in CI: case-sensitivity issue

TL;DR: Your local filesystem is case-insensitive, so import Button from './button' resolves even when the file is really Button.js. CI runners use case-sensitive filesystems, so the same import fails with ENOENT. Find the casing mismatch with git ls-files, fix it with git mv (or fix the import), and the CI error goes away. One rename, no code changes.

Not specified by the original author.

excel import date format mismatch error compliance matrix: how to fix it

An Excel date format mismatch on compliance matrix import means the dates are text in one format while the importer expects another. Standardize the date column to a single unambiguous format like YYYY-MM-DD before importing. Regional date formats are the classic trap, 03/04 means different things in the US and Europe.

excel import date format mismatch error compliance matrix

When to use this skill

• Date columns import wrong or fail
• Dates flip day and month on import

When not to use this skill

• Non-date columns fail (a different format issue)
• The import fails on structure (a parsing issue)

Tool compatibility

Compliance matrix Excel imports with date fields. Related area: CSV and Excel data import pipelines. Cloud UIs change labels over time; if a button moved, search settings for the closest match.

Before you start

• Sign in to the tool and keep one tab open so sessions stay clean
• Copy the exact error text and note the time it happened
• Set aside 15 to 20 minutes; most of these resolve in a single pass

Quick diagnosis

Make sure this is the right skill before you invest the 15 minutes.

• If you are dealing with date columns import wrong or fail, start at step 1 below.
• If instead non-date columns fail (a different format issue), stop here; you need a different skill.
• If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

Fix it in steps

1. Inspect the date column

Open the Excel file and check how dates are actually formatted and stored.

Expected: mixed formats or text-stored dates revealed.

2. Standardize to YYYY-MM-DD

Convert the whole column to one unambiguous format.

Expected: every date reads the same way everywhere.

3. Confirm dates are real dates

Check that Excel treats the cells as dates, not text.

Expected: date type confirmed, not text.

4. Re-import the matrix

Upload the standardized file.

Expected: dates import correctly.

Confirm each step worked

Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.

• Step 1 (inspect the date column): Expected: mixed formats or text-stored dates revealed.
• Step 2 (standardize to yyyy-mm-dd): Expected: every date reads the same way everywhere.
• Step 3 (confirm dates are real dates): Expected: date type confirmed, not text.
• Step 4 (re-import the matrix): Expected: dates import correctly.

Quick recap

1. Inspect the date column
2. Standardize to YYYY-MM-DD
3. Confirm dates are real dates
4. Re-import the matrix

Still stuck?

Gather three things: the exact error text, the time it happened, and what changed just before it broke. Check the vendor status page for an active incident. Then open a support ticket with those three things; it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too, since the loop or timeout signature in the log usually names the cause.

Variant phrasings

excel date format mismatch import

YYYY-MM-DD removes all ambiguity. If this matches what you saw, the steps above apply as written.

compliance matrix dates wrong import

Text-stored dates are the sneaky variant. If this matches what you saw, the steps above apply as written.

Why it happens

Excel stores dates as numbers but displays them per regional settings, while importers parse the displayed text. A US-formatted date read by a European-expecting parser flips day and month or fails outright.

Edge cases

• Text-stored dates look right but import wrong, convert the cell type
• Empty date cells can error, decide on a blank policy first
• Time components in dates confuse date-only fields, strip them

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cvvrs2Mu4PriK5O2ug1lyQ

Resolved from the public thread: https://vectle.com/posts/pst_cvvrs2Mu4PriK5O2ug1lyQ

Thread query: excel import date format mismatch error compliance matrix

TL;DR: