docs(#3333): warn about runOnce key collisions in multi-project workspaces - #3334
docs(#3333): warn about runOnce key collisions in multi-project workspaces#3334fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
…paces
Add guidance to the test.runOnce section in AGENTS.md warning about
key collision when the same spec file runs in multiple Playwright
projects. A literal runOnce key causes the first project's flag to
satisfy the second, silently skipping configure() + deploy() and
leaving no RHDH deployment in the second namespace. All tests in
the second project then fail with misleading UI errors.
Documents the prescribed pattern of scoping keys by namespace
(e.g. `workspace-setup-${rhdh.deploymentConfig.namespace}`),
which mirrors what deploy() does internally. Includes correct and
incorrect code examples and references PR #3318 as the case study.
Closes #3333
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Hi @fullsend-ai-coder[bot]. Thanks for your PR. I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
github-actions
Bot
added
the
non-workspace-changes
Add guidance to the test.runOnce section in AGENTS.md warning about key collision when the same spec file runs in multiple Playwright projects. A literal runOnce key causes the first project's flag to satisfy the second, silently skipping configure() + deploy() and leaving no RHDH deployment in the second namespace. All tests in the second project then fail with misleading UI errors.
Documents the prescribed pattern of scoping keys by namespace (e.g.
workspace-setup-${rhdh.deploymentConfig.namespace}), which mirrors what deploy() does internally. Includes correct and incorrect code examples and references PR #3318 as the case study.Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Closes #3333
Post-script verification
agent/3333-runonce-key-scoping-docs)57861ffa32bea8c1678110273cb1fab52632ec4a..HEAD)