QA Automation

Work this role can support

• Write Playwright or Cypress tests for named user journeys and browser targets
• Add API contract checks for status codes, payload schemas, and authorization failures
• Build deterministic fixtures and mocks for approved accounts and external dependencies
• Classify flaky tests using traces, screenshots, videos, and repeatable failure evidence

Controls to set first

• The owner defines release-blocking scenarios and decides whether failed checks may be waived
• Test accounts use synthetic data and carry no production payment or privileged access
• Retries cannot hide a failed assertion; quarantine requires a reason and owner approval
• CI logs and retained artifacts must exclude tokens, credentials, and personal data

Practical launch plan

1. Name one critical journey, its browser matrix, test environment, and expected checkpoints
2. Provide the existing CI workflow, synthetic accounts, selectors, and fixture-reset method
3. Automate one deterministic path and compare its assertions with the manual test case
4. Review failure artifacts and quarantine rules before making the suite a required check