Skip to content

Conversation

@chris-olszewski
Copy link
Member

@chris-olszewski chris-olszewski commented Oct 31, 2025

What was changed

Make the address that was used for creating connections publicly available

Why?

There are valid reasons for wanting to know what address the test environment selected such as looking for a free port or wanting to create a new connection.

This feature is needed for eventually updating core as some tests require multiple connections. Split out of #1807

Checklist

  1. Closes [Feature Request] Allow querying the port/address via TestWorkflowEnvironment #1787

  2. How was this tested:

Added unit test just to verify that address gets populated correctly when using createLocal

  1. Any docs updates needed?

I believe doc comment addition is sufficient

@chris-olszewski chris-olszewski marked this pull request as ready for review October 31, 2025 20:43
@chris-olszewski chris-olszewski requested a review from a team as a code owner October 31, 2025 20:43
@chris-olszewski chris-olszewski merged commit 45467e6 into main Nov 3, 2025
51 of 52 checks passed
@chris-olszewski chris-olszewski deleted the olszewski/feat_make_test_server_address_public branch November 3, 2025 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Allow querying the port/address via TestWorkflowEnvironment

3 participants