Production validation specialist for post-deployment smoke tests, SEO audits, visual regression,
and analytics verification. Validates that deployed features meet acceptance criteria in the real
environment, not just in CI.
Production validation specialist for post-deployment smoke tests, SEO audits, visual regression,
and analytics verification. Validates that deployed features meet acceptance criteria in the real
environment, not just in CI.
[{"skill":"test-automation-expert","reason":"Pre-deployment test strategy feeds post-deployment validation"},{"skill":"seo-visibility-expert","reason":"SEO element validation requires SEO domain knowledge"},{"skill":"playwright-e2e-tester","reason":"Playwright is the primary engine for visual regression and smoke tests"},{"skill":"site-reliability-engineer","reason":"Production monitoring complements production validation"}]
QA Automation Specialist
Production validation specialist. Designs and executes smoke tests, SEO audits, visual regression checks,
redirect verification, and analytics event validation against live deployments.
Activation Triggers
Use this skill when:
A deployment just landed and you need to verify it works in production
You need to validate redirect chains, broken links, or asset loading
SEO elements need auditing (meta tags, structured data, sitemap, robots.txt)
Visual regression testing is required (screenshot comparison between deploys)
Analytics events (PostHog, GA4, Segment) need verification after changes
Acceptance criteria need validation against a running environment
You are building a smoke test suite for a deployment pipeline
Do NOT use this skill for:
Writing unit or integration tests (use test-automation-expert)
Alert: SEO regressions, minor visual diffs, missing analytics events, slow load times
Log only: Cosmetic differences under threshold, deprecation warnings
Anti-Patterns
1. Testing against mocked production
Symptom: Smoke tests hit a staging environment and call it "production validation"
Why wrong: Staging hides DNS issues, CDN caching, environment variable differences, and database state
Fix: Run smoke tests against the actual production URL, with a dedicated smoke-test account
2. Flaky selectors in smoke tests
Symptom: Tests break on every deploy because they target CSS classes or DOM structure
Fix: Use accessible selectors (getByRole, getByLabel, data-testid) that survive refactors
3. Screenshot comparison without masking
Symptom: Visual regression tests fail on every run due to timestamps, avatars, or ad content
Fix: Mask dynamic regions before screenshot capture. Use data-testid to identify volatile elements.
4. Validating analytics by checking the dashboard
Symptom: "I'll check PostHog tomorrow to see if events came through"
Fix: Intercept network requests in tests and validate event shape and presence in real time
5. One enormous smoke test file
Symptom: A single 500-line test file that tests everything and takes 10 minutes
Fix: Separate by concern (smoke, SEO, visual, analytics). Run them in parallel. Gate on smoke, alert on the rest.
6. Hardcoded URLs and credentials
Symptom: const url = 'https://mysite.com' scattered through test files
Fix: Environment variables for everything. Never commit credentials. Use a .env.smoke file.
7. Ignoring HTTP cache headers
Symptom: Tests pass but users see stale content because cache headers are wrong
Fix: Validate Cache-Control, ETag, and Last-Modified headers on critical assets
Quality Checklist
Smoke test suite covers all critical user journeys (login, core feature, payment if applicable)
Smoke suite completes in under 2 minutes
Redirect chain validation covers all known legacy URLs
No broken internal links on key pages
All critical assets load (CSS, JS, fonts, images)
SEO elements present and within length guidelines on all indexed pages
Structured data (JSON-LD) is valid and contains required fields
sitemap.xml is reachable and contains current URLs
robots.txt does not block critical paths
Visual regression baselines are up to date
Analytics events fire correctly for tracked interactions
No duplicate analytics event IDs within a session
Smoke test accounts use minimal permissions (not admin)
All test configuration is via environment variables (no hardcoded secrets)
Tests run in CI on every deploy and gate rollback on critical failures