Commit 22e7dfbb authored by Ken Zangelin's avatar Ken Zangelin
Browse files

fix: validate notifiedAt against the with-millis date format 

Brokers send notifiedAt as ISO-8601 with millisecond precision (e.g.
'2026-05-04T13:31:05.403Z') — the file already defines
${date_format_with_millis} for exactly this case but 'Wait for
notification and validate it' validates against ${date_format} (no
millis), so 'Is Date' returns False and every CSR-subscription
notification test (047_*) fails after the type check passes.

Switch the validator to ${date_format_with_millis} which matches
what brokers actually emit.
parent 9b63b450

resources/NotificationUtils.resource

+1 −1
Original line number Diff line number Diff line
@@ -65,7 +65,7 @@ Wait for notification and validate it 
    Output Notification    ${notification}    ${notification_headers}    Wait for notification

    Should Be Equal    ${notification}[type]    ${notification_type}

    Should Be Equal    ${notification}[subscriptionId]    ${expected_subscription_id}

    ${is_date}=    Is Date    ${notification}[notifiedAt]    ${date_format}

    ${is_date}=    Is Date    ${notification}[notifiedAt]    ${date_format_with_millis}

    Should Be True    ${is_date}

    ${index}=    Set Variable    0

    FOR    ${expected_context_source_registration_id}    IN    @{expected_context_source_registration_ids}