1---2name: workflow-testing3description: Use when validating automation builds before launch or after significant changes.4---5
6# Workflow Testing & QA Skill
7
8## When to Use
9- Any new automation or major revision prior to go-live.
10- Regression testing after data, asset, or logic changes.
11- Investigating deliverability, conversion, or routing anomalies.
12
13## Framework
141. **Unit Tests** – confirm each branch, wait step, and action path with seed contacts.
152. **Integration Tests** – verify webhook/API calls, CRM updates, enrichment, scoring.
163. **Content QA** – links, tracking, personalization tokens, accessibility, localization.
174. **Compliance** – consent, suppression, GDPR/CASL/CCPA rules, regional requirements.
185. **Performance** – throttle checks, concurrency, error handling, failover.
19
20## Checklist
21- Seed list matrix (personas, stages, regions, consent flags).
22- Device/browser testing for email/SMS/push rendering.
23- Logging + alerting validation.
24- Rollback and kill switches documented.
25
26## Templates
27- QA evidence log (screenshot, recipient, status, owner).
28- Incident runbook for automation failures.
29- Release checklist referencing stakeholders.
30
31## Tips
32- Automate regression tests via APIs or synthetic users.
33- Store test data separately and purge regularly to avoid reporting noise.
34- Use feature flags to stage rollouts before full scale.
35
36---