QA Automation Resources

Playwright: reducing flaky UI automation

Start with resilient role, label and test-id locators. Wait for meaningful application states such as a spinner disappearing, a response completing or a control becoming enabled—not arbitrary sleep calls. Keep test data isolated and use page objects only for stable, reusable actions.

See the Playwright framework case study →

API testing checklist

• Validate authentication, status codes, headers and response contracts.
• Cover successful, invalid, boundary and permission-based scenarios.
• Verify important side effects with database or downstream-service checks.
• Use correlation IDs and clear failure logs to isolate integration issues.

See the API quality case study →

Salesforce QA: what needs coverage

Test business rules as well as screens: CPQ bundle and discount logic, approvals, lead conversion, permissions, reports, integrations and data transitions. Combine UI validation with API and SOQL checks so failures are detected at the correct layer.

See the Salesforce QA case study →

CI/CD quality gates

Run fast smoke coverage on pull requests, then schedule broader regression suites. Publish trace files, screenshots and clear reports on failure. Treat unstable tests as quality work: investigate the product state, test data and locator strategy before adding retries.

Need an automation-focused QA engineer?

I work across Playwright, Selenium, REST and GraphQL APIs, SQL, Salesforce and CI/CD quality engineering.