Skip to main content
Generalgtmagents

workflow-testing

Use when validating automation builds before launch or after significant

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--workflow-testing
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/marketing-automation/skills/workflow-testing/SKILL.md -o .claude/skills/workflow-testing.md

Drops the SKILL.md into .claude/skills/workflow-testing.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Workflow Testing & QA Skill

When to Use

  • Any new automation or major revision prior to go-live.
  • Regression testing after data, asset, or logic changes.
  • Investigating deliverability, conversion, or routing anomalies.

Framework

  1. Unit Tests – confirm each branch, wait step, and action path with seed contacts.
  2. Integration Tests – verify webhook/API calls, CRM updates, enrichment, scoring.
  3. Content QA – links, tracking, personalization tokens, accessibility, localization.
  4. Compliance – consent, suppression, GDPR/CASL/CCPA rules, regional requirements.
  5. Performance – throttle checks, concurrency, error handling, failover.

Checklist

  • Seed list matrix (personas, stages, regions, consent flags).
  • Device/browser testing for email/SMS/push rendering.
  • Logging + alerting validation.
  • Rollback and kill switches documented.

Templates

  • QA evidence log (screenshot, recipient, status, owner).
  • Incident runbook for automation failures.
  • Release checklist referencing stakeholders.

Tips

  • Automate regression tests via APIs or synthetic users.
  • Store test data separately and purge regularly to avoid reporting noise.
  • Use feature flags to stage rollouts before full scale.