test: add coverage for mqtt/status date parsing

[augard]

Summary

• add focused tests for millisecond timestamp parsing via DateValue<TimeIntervalDateFormatter>
• add focused tests for compact merged timestamp parsing via DateValue<MergedDateFormatter>
• add decode coverage for VehicleMQTTStatusResponse.latestUpdateTime + state mapping

Why

Recent MQTT/status integration changed timestamp handling paths without direct tests.

Verification

• Added 3 focused XCTest cases in KiaTests/MockVehicleDataTests.swift
• Full test run blocked in this environment previously by package/network constraints

[github-actions]

There is a problem with the Gemini CLI PR review. Please check the action logs for details.

[augmentcode]

🤖 Augment PR Summary

Summary: Adds focused XCTest coverage for MQTT/status timestamp parsing and response decoding.

Changes: (1) Test millisecond-epoch string decoding via DateValue<TimeIntervalDateFormatter>.

(2) Test compact yyyyMMddHHmmss decoding via DateValue<MergedDateFormatter>.

(3) Add decode coverage for VehicleMQTTStatusResponse including latestUpdateTime key mapping.

Why: Protect recent timestamp-handling changes with direct unit tests.

Notes: Keeps tests small/isolated to avoid needing full integration/network setup.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Calendar(identifier: .gregorian).date(from:) returns an optional Date; consider unwrapping the result so the test fails loudly if the components can’t be converted and the subsequent equality check is against a non-optional value.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[Copilot]

Pull request overview

Adds targeted XCTest coverage around the recent MQTT/status timestamp parsing changes and related decoding paths in the KiaMaps API model layer.

Changes:

• Add a unit test validating millisecond-epoch timestamp string decoding via @DateValue<TimeIntervalDateFormatter>.
• Add a unit test validating compact UTC timestamp decoding via @DateValue<MergedDateFormatter>.
• Add a decode test exercising VehicleMQTTStatusResponse payload decoding and basic state mapping.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

testVehicleMQTTStatusResponseDecodesLatestUpdateTimeAndState doesn’t currently assert anything about latestUpdateTime/lastUpdateTime, so it won’t catch regressions in the CodingKeys mapping or MergedDateFormatter parsing. Add an assertion that response.lastUpdateTime matches the expected UTC date represented by "20250901202513" (or rename the test if time decoding is intentionally out of scope).

Suggested change

	var components = DateComponents()
	components.year = 2025
	components.month = 9
	components.day = 1
	components.hour = 20
	components.minute = 25
	components.second = 13
	components.timeZone = TimeZone(secondsFromGMT: 0)
	let expected = Calendar(identifier: .gregorian).date(from: components)
	XCTAssertEqual(response.lastUpdateTime, expected)

[Copilot]

expected is a Date? from Calendar.date(from:); if it were ever nil, the assertion failure would be less clear. Consider unwrapping with XCTUnwrap (or assert not-nil) before comparing to payload.latestUpdateTime so failures point to calendar construction vs decoding.

Suggested change

	let expected = Calendar(identifier: .gregorian).date(from: components)
	let expected = try XCTUnwrap(Calendar(identifier: .gregorian).date(from: components))