Use configured test environments in client integration suites - #2285
Draft
THardy98 wants to merge 2 commits into
Draft
Use configured test environments in client integration suites#2285THardy98 wants to merge 2 commits into
THardy98 wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Several integration suites still created workers and clients with implicit localhost defaults, so the envconfig support added in #2163 could not run them against Temporal Cloud.
This migrates the client-, codec-, bundler-, interceptor-, and payload-oriented suites to one environment-owned connection and namespace per file. Worker and client lifecycles now share that environment, task queues are unique for persistent namespaces, and existing mock-only paths remain unchanged.
Validation: focused ESLint and Prettier checks pass.
pnpm --dir packages/test buildreaches TypeScript and reports only the existingActivityExecutionStatus.PAUSEDmismatch caused by the locally advancedpackages/core-bridge/sdk-coresubmodule; no errors remain in these test files.