mcpField
W
workflow-testing

workflow-testing

github.com/gtmagentsTesting & quality42865 installsUpdated 30w ago
Repository

About workflow-testing

workflow-testing is a skill for validating automations before launch and performing ongoing QA, intended for marketing operations and workflow teams. It covers branching, integrations, content, compliance, and performance, with checklists and incident templates.

Key features

  1. 01Test branches and actions with seed contacts
  2. 02Verify webhooks, APIs, and CRM updates
  3. 03Check links, personalization, and accessibility
  4. 04Validate consent, suppression, and regional compliance
  5. 05Test throttling, concurrency, and error handling

Use cases

  1. 01QA new automations before launch
  2. 02Run regression tests after data or logic changes
  3. 03Investigate deliverability, conversion, or routing anomalies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill workflow-testing

After installing, type/workflow-testingin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported