canary-execution

What problem does it solve?

This Skill defines how test suites can validate both local environments and deployed canary targets without duplicating test logic or reusing the wrong entry point. It keeps smoke and E2E checks safe, fast, and deployment-aware by separating local dependency bootstrapping from canary execution.

Core Features & Use Cases

• Separate local and canary modes through a dedicated test entry point so the same tests can run against localhost or TEST_TARGET_URL.
• Enforce canary eligibility rules for critical smoke and E2E tests, including read-only or self-cleaning behavior and no database bootstrapping in canary mode.
• Support deploy-gate workflows with strict performance budgets, clear gating semantics, and safety linting for write operations.
• Use case: promote a critical checkout or login flow to a post-deploy canary suite while keeping the regular local smoke job unchanged.

Quick Start

Ask the assistant to audit your smoke and E2E tests, split them into local and canary paths, and add a dedicated canary entry point that reads TEST_TARGET_URL and respects the 60-second deploy-gate budget.