Fix: getResponseHeaders() returns empty struct after setup()

[homestar9]

MockRequestContext.getResponseHeaders() always returns an empty struct {} in integration tests, even after calling setHTTPHeader(). This causes test assertions on response headers to fail unexpectedly when setup() is called between tests.

Note: I didn't see a specific test file for MockRequestContext, so I added my test to RequestContextTest.

Jira Issues

https://ortussolutions.atlassian.net/browse/COLDBOX-1380

Type of change

Please delete options that are not relevant.

• [x ] Bug Fix

Checklist

• [ x] My code follows the style guidelines of this project cfformat
• [ x] I have commented my code, particularly in hard-to-understand areas
• [x ] I have added tests that prove my fix is effective or that my feature works
• [x ] New and existing unit tests pass locally with my changes

[Copilot]

Pull request overview

This PR fixes a bug in MockRequestContext where getResponseHeaders() always returns an empty struct even after setHTTPHeader() is called. The issue occurs because MockRequestContext's overridden setHTTPHeader() method only updates the mock-specific cbox_headers collection but doesn't update the variables.responseHeaders that getResponseHeaders() reads from.

Changes:

• Updated MockRequestContext.setHTTPHeader() to populate variables.responseHeaders when headers are set
• Added test coverage to verify getResponseHeaders() returns headers set via setHTTPHeader()

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
system/testing/mock/web/context/MockRequestContext.cfc	Added line to sync responseHeaders when setHTTPHeader() is called with a header name
tests/specs/web/context/RequestContextTest.cfc	Added test case to verify MockRequestContext populates responseHeaders correctly

[lmajano]

gracias amigo