Expertise
QA expertise
The kinds of testing I do, where I apply each one and the tools I use. Manual and functional testing is my core; technical testing supports it.
Capabilities
What I bring to a team
- 01 · Core
Manual & functional testing
This is the core of my work. I manually test web and mobile applications against business requirements, covering critical user journeys such as browsing, customization, cart, checkout, payment and order tracking.
- Test case and scenario design from requirements and FRDs
- Positive, negative and edge-case coverage on business-critical flows
- Web and native mobile app testing on every release
- UI/UX verification against agreed designs
- 02 · Core
Regression & release validation
I protect existing functionality while new features ship. Before anything goes to production it passes smoke, sanity and full regression cycles and gets a QA sign-off.
- Smoke and sanity checks on every build
- Regression cycles before each release
- Retesting and verifying fixes
- Release sign-off
- 03 · Core
Defect management
Defects I log are clear and reproducible, prioritized with the team and tracked through to closure, so developers can fix them fast and nothing slips through.
- Reproducible steps, evidence and expected vs. actual results
- Severity and priority agreed with developers and product
- Full lifecycle tracking in Jira and Azure DevOps
Supporting skills
API & integration testing
I validate APIs and third-party integrations, using system and application logs to confirm data moves correctly between services.
Performance testing
I build load scenarios in Apache JMeter to see how the backend behaves under different user loads and to find bottlenecks before peak traffic does.
Test automation
Automation supports my manual testing. I use Cypress to take repetitive regression checks off the manual cycle, and I am currently learning Playwright with AI-assisted testing.
Testing types
Where and how I apply each type
I describe each testing type by where I use it, rather than rating myself with skill percentages.
Functional
Does the product do what the business needs?
- Functional testing
- Validating every feature against requirements on web and mobile app
- Requirements validation
- Reviewing FRDs and requirements for gaps before development starts
- End-to-end testing
- Complete ordering journeys, from browsing the menu to tracking the order
- System testing
- Validating the whole application as an integrated product
- Integration testing
- Payment, delivery and third-party services, verified through logs
- UI/UX verification
- Layout, content and interaction checked against agreed designs
Change & release
Did this change break anything that already worked?
- Smoke testing
- Fast check that a new build is stable enough to test
- Sanity testing
- Focused check of a fix or a small change
- Retesting
- Confirming reported defects are actually fixed
- Regression testing
- Protecting existing functionality before every release
- Release validation
- Final verification and QA sign-off before production
Technical
Is it correct beneath the UI, and does it hold up under load?
- API testing
- Status codes, payloads, business rules and error handling
- Database testing
- Checking stored data against UI and API behavior using SQL
- Performance testing
- Load scenarios in Apache JMeter to find backend bottlenecks
- Log analysis
- Tracing data flow between integrated services
Platform & experience
Does it work for every user, on every surface?
- Web application testing
- Responsive customer-facing web ordering platforms
- Mobile application testing
- Native app releases across devices and screen sizes
- Multi-market testing
- Localized menus, flows and configurations for different regions
- Usability testing
- Flagging friction in critical flows from the user’s point of view
Technical testing
API, performance & automation
API testing
A screen can look right while the API underneath returns the wrong data, so I validate the service layer as well.
- Request and response validation
- Status-code verification
- Payload and schema checks
- Positive and negative scenarios
- Edge cases and error handling
- Business-rule validation
- Cross-checking API results against the database
Performance testing
High-traffic ordering platforms have to stay fast at peak hours. I use JMeter to see how the backend behaves before real users push it.
- Load scenarios that simulate concurrent users
- Response-time validation
- Behavior under different user loads
- Identifying backend bottlenecks
- Reporting findings to engineering
- Apache JMeter
Test automation
Automation supports my testing rather than replacing it. Its job is to make regression faster and more repeatable so I have more time for exploratory and risk-based checks.
- Automating repetitive regression checks with Cypress
- Stable, repeatable checks for critical flows
- Faster validation of new builds
- Learning Playwright with AI-assisted testing
- Cypress
- Playwright
Tools
Tools & platforms
| Tool | Area | How I use it |
|---|---|---|
| Jira | Test & defect management | Defect lifecycle, sprint boards and test tracking |
| Azure DevOps | Test & defect management | Work items, bug tracking and sprint boards (Dubai South) |
| Apache JMeter | Performance | Load testing and backend bottleneck analysis |
| Cypress | Automation | Automated regression checks for web flows |
| PlaywrightLearning | Automation | Cross-browser automation with AI-assisted testing |
| SQL | Data | Database validation and data verification |
| System & application logs | Analysis | Tracing integrations and investigating production issues |
Workflow
My QA workflow
- 01
Understand requirements
Review FRDs and user stories and raise gaps early.
- 02
Plan
Agree on scope, risk areas, platforms and environments.
- 03
Design tests
Write test cases for happy paths, negatives and edge cases.
- 04
Execute
Run functional, integration and API tests on web and app.
- 05
Report defects
Log clear, reproducible defects and triage them with the team.
- 06
Retest
Verify each fix in the environment where it failed.
- 07
Regression
Confirm nothing that already worked has broken.
- 08
Sign off
Validate the release and give QA approval for production.
- 09
Support
Monitor after release and handle AMS issues.
Contact
Shipping something that has to work?
I'm open to Senior SQA Engineer roles and QA collaborations. Tell me about the product, the team and the release you're working toward.