Connect to Test Environment
In brief: Procure and connect to the test environment used by automation workflows—blocked until
connect-to-test-env.policy.md(or--policyoverride) exists.
When to use
Standalone when you need an environment prepared, or automatically as a dependency of Create tests, Smart regression, ExploreChimp, Fix coverage gaps, and composites. This is the only catalog workflow with requiresPolicy=true.
Prompt
/testchimp connect to test environment
/testchimp connect to test environment --policy connect-to-test-env-staging.policy.md
Scope
Driven by policy sections for feature branch, default branch, and CI (ephemeral PR sandbox vs shared staging, credentials, bootstrap). Prompt may refine which target.
Policy (required)
Must have plans/knowledge/policies/connect-to-test-env.policy.md (or another *.policy.md with workflow-id: connect-to-test-env, or --policy). Not auto-seeded by init—author with /testchimp create policy connect-to-test-env. Skill provides a skeleton checklist (feature-branch / default-branch / CI).
Until this exists, dependent workflows show Missing config in the platform Workflows list.
What it does
Follows the policy to provision or connect (preview URL, Bunnyshell/EaaS, persistent QA, etc.), sets BASE_URL (and related secrets) for subsequent steps, and records decisions for reproducibility. See Init — Environments and Bunnyshell.