Missing integration scenario JSON in the TIMEZONE aware PR

[authorjapps]

Here is this open PR: #776 (comment). Only missing is a full integration test scenario using this new feature.

Once added, we'll run the CI, then merge the PR on Green.

[Huzi-06]

Added the missing integration test scenario — see comment on #771: #771 (comment)

Preview below:

Hi @officialasishkumar @authorjapps — I saw #784 was still open asking for the missing integration test scenario for this timezone-aware datetime fix, so I put one together.

It's on my fork here: Huzi-06/zerocode branch add-timezone-integration-test
Commit: Huzi-06@6abd761

It adds http-testing-examples/src/test/resources/helloworld_date/hello_world_date_timezone_aware_test.json, covering all four supported formats from the acceptance criteria:

• ISO datetime with offset (+05:30)
• ISO UTC/Zulu (Z)
• RFC-1123 HTTP date format
• Legacy local datetime (no timezone) — for backward compatibility

Ran locally against this branch and both tests pass (HelloWorldDateAfterBeforeTest). Happy to have this cherry-picked into #771 directly, or I can open it as a small follow-up PR, whichever's easier for you.

Scenario:

{
    "scenarioName": "Assert timezone-aware datetime parsing across ISO offset, UTC Zulu, RFC-1123 and legacy local formats",
    "steps": [
        {
            "name": "assert_iso_offset_format",
            "url": "/users/octocat",
            "method": "GET",
            "request": {},
            "assertions": {
                "status": 200,
                "body": {
                    "created_at": "$LOCAL.DATETIME.BEFORE:2019-07-06T22:37:15+05:30"
                }
            }
        },
        {
            "name": "assert_iso_utc_zulu_format",
            "url": "/users/octocat",
            "method": "GET",
            "request": {},
            "assertions": {
                "status": 200,
                "body": {
                    "created_at": "$LOCAL.DATETIME.BEFORE:2019-07-06T17:07:15.000Z"
                }
            }
        },
        {
            "name": "assert_rfc_1123_http_date_format",
            "url": "/users/octocat",
            "method": "GET",
            "request": {},
            "assertions": {
                "status": 200,
                "body": {
                    "created_at": "$LOCAL.DATETIME.BEFORE:Sat, 06 Jul 2019 17:07:15 GMT"
                }
            }
        },
        {
            "name": "assert_legacy_local_format_backward_compatibility",
            "url": "/users/octocat",
            "method": "GET",
            "request": {},
            "assertions": {
                "status": 200,
                "body": {
                    "created_at": "$LOCAL.DATETIME.BEFORE:2019-07-06T17:07:15.000"
                }
            }
        }
    ]
}

[authorjapps]

Added the missing integration test scenario — see comment on #771: #771 (comment)

Preview below:

Hi @officialasishkumar @authorjapps — I saw #784 was still open asking for the missing integration test scenario for this timezone-aware datetime fix, so I put one together.

It's on my fork here: Huzi-06/zerocode branch add-timezone-integration-test Commit: Huzi-06@6abd761
...

@Huzi-06, scenario looks good, just we need to run via the CI pipeline.
Is it not allowing you to push to the existing PR directly?

If not, I can add you as Collaborator and give it a try... Can you please let me know?

[Huzi-06]

Yep, exactly, I don't have write access to @officialasishkumar's fork, so I can't push to the PR branch directly.

If @officialasishkumar has "Allow edits from maintainers" enabled on #771, that might be the lightest way to let me push without a full collaborator add, worth checking first. But if that's not enabled or doesn't work for some reason, being added as a collaborator works too, happy to give it a try either way!

[authorjapps]

Yep, exactly, I don't have write access to @officialasishkumar's fork, so I can't push to the PR branch directly.

Added you here, click and join, then give it a try and let us know @Huzi-06 .