canary-execution

Separate local smoke tests from post-deploy canary execution via dedicated entry point and TEST_TARGET_URL with 60-second budget.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill canary-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary-execution
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/canary-execution
Command: npx skills add https://github.com/app-vitals/shipwright --skill canary-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about canary-execution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the same E2E smoke tests against both localhost and a deployed canary target?

Separate local smoke testing from canary execution by using a dedicated canary entry point that reads TEST_TARGET_URL. This allows the same test code to run against localhost in development or a deployed target in production gating.

What are the eligibility rules for adding E2E tests to a post-deploy canary suite?

Canary E2E tests must be read-only or self-cleaning, require zero local database bootstrapping in canary mode, and respect a strict 60-second suite budget for deploy gating.

How do I split existing smoke tests into local and canary execution paths?

Audit your smoke and E2E tests to separate local dependency bootstrapping from canary execution, then add a dedicated canary entry point that enforces read-only behavior and the 60-second deploy-gate budget.

Why do my canary tests fail when they try to bootstrap the database during deployment?

Canary tests fail because canary execution requires zero local database bootstrapping. You must separate local dependency bootstrapping from canary mode to keep post-deploy checks safe and deployment-aware.

Can I use canary test execution as a deploy gate for critical checkout flows?

Yes, you can promote critical checkout or login flows to a post-deploy canary suite. The suite enforces strict performance budgets, clear gating semantics, and safety linting for write operations.