QA & Test Automation
My QA background gives me a quality-focused approach to delivery. I treat testing as part of the development process rather than something that happens only before release.
Testing experience
- Functional testing
- Regression testing
- Integration testing
- API testing
- UI testing
- End-to-end testing
- UAT coordination
- Cross-browser testing
- Mobile testing
- Test case design
- Bug reporting
- Release validation
Automation approach
Page Object Model
Reusable page objects keep suites maintainable as the product grows.
API + UI layers
Fast API checks for business rules, focused UI tests for critical user journeys.
CI/CD pipelines
Tests run on every change so regressions are caught before release, not after.
Tools & technologies
Playwright, Selenium, Cypress, Appium, Python, Pytest, API automation, CI/CD pipelines
Frequently asked questions
Playwright, Selenium or Cypress?
Playwright is my default for new web projects because of its speed, auto-waiting and multi-browser support. Selenium suits existing suites and wide language support; Cypress is productive for front-end-heavy teams.
What should be automated first?
Start with the workflows that would hurt most if they broke, such as login, payments, orders and core APIs, then expand regression coverage release by release.