Skip to content

Use configured test environments in client integration suites - #2285

Draft
THardy98 wants to merge 2 commits into
mainfrom
agent/cloud-client-env-migration
Draft

Use configured test environments in client integration suites#2285
THardy98 wants to merge 2 commits into
mainfrom
agent/cloud-client-env-migration

Conversation

@THardy98

@THardy98 THardy98 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

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 build reaches TypeScript and reports only the existing ActivityExecutionStatus.PAUSED mismatch caused by the locally advanced packages/core-bridge/sdk-core submodule; no errors remain in these test files.

@THardy98 THardy98 added the skip-changelog No changelog is necessary for this PR. label Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog No changelog is necessary for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant