Date comparison failure: expect(Date()).to(equal(Date())) inconsistent across locales

Resolution

Nimble does not provide a built-in API to specify a time zone for date expectations. Because Nimble compares Date instances using timeIntervalSinceReferenceDate, the comparison itself is zone-independent; however, the instantiation of those dates from ISO strings without time zone offsets is not. When a string lacks an offset, the system parses it using the local time zone of the environment, leading to different absolute timestamps on a developer's machine versus a UTC-configured CI server.

Likely Explanation

The inconsistency is not a failure of the Nimble matcher, but a side effect of how DateFormatter or ISO8601DateFormatter behaves when the input string is "naive" (lacks a time zone). If the input is "2026-09-18T10:00:00", the system assumes the local time zone. A developer in EST and a CI server in UTC will produce two different Date objects representing different moments in absolute time, causing the equal() assertion to fail.

Implementation Steps

To ensure portability across environments, you must normalize the parsing logic rather than the assertion. Use one of the following approaches:

• Force UTC Parsing: Explicitly set the time zone of your DateFormatter to UTC before creating the Date objects.
• Use Explicit ISO Strings: Append Z (for UTC) or a specific offset (e.g., +05:00) to your test strings to remove ambiguity.
• Manual Normalization: If you cannot change the source strings, wrap the parsed dates in a helper that converts them to a common reference point before passing them to expect().

CI vs. Local Impact

Tests that pass locally but fail in CI (or vice versa) are typically "flaky" due to this environmental dependency. Relying on the system locale makes tests non-deterministic. By forcing UTC parsing, you ensure that the timeIntervalSinceReferenceDate remains identical regardless of where the binary is executed.

Diagnostic Requirement

To provide a more specific code snippet, please clarify: Which class are you using to parse the ISO strings (e.g., ISO8601DateFormatter, DateFormatter, or a third-party library)?