6 years across QA and technical support, including 4 years focused on testing.
I validate APIs, backend data and integrations - connecting user flows with SQL, logs and release checks.
Read the examples right here. Open a report, walk through a test case, or explore how I break down coverage.
Two portfolio examples, adapted from the original issue reports.
The login page links to a missing route. A logged-out user cannot start the password reset flow.
The password reset page opens with an email field and submit button. Its title and heading identify the reset flow.
A 404 Not Found page appears because the link points to a missing route.
The source report references a screenshot and HAR file. Those attachments are not included in this portfolio export.
After a payment-provider timeout, the UI shows an error and empties the cart while an order remains pending in the backend. The user receives no confirmation and cannot retry without adding the items again.
The cart stays intact, no order is created, and the user can retry payment.
The cart is cleared and an order exists with Pending status. The user must re-add the items to retry.
Adapted reproduction outline: the export does not include a verified timeout setup or its referenced HAR and screenshots. The expected order behavior depends on the product’s payment requirements.
Authentication and promotion examples. Expand a case to read its steps.
A verified user exists and is logged out with a clean session. Use valid_user@example.com and its valid password. Exercise both Remember me states.
| Action | Expected result |
|---|---|
| 1. Open /login | HTTP 200. Email and password fields are visible; no authenticated user menu. |
| 2. Enter valid credentials | Validation passes. Password remains masked; no inline errors. |
| 3. Set Remember me | The selected state remains after blur or scrolling. |
| 4. Submit login | One POST /auth/login request. Credentials are absent from the URL; progress is indicated. |
| 5. Inspect the response | HTTP 200 with a session cookie or token; no error notification. |
| 6. Check the redirect | The dashboard or intended private page opens with the correct URL and heading. |
| 7. Check authenticated UI | User menu is visible, the login link is hidden, and private content is accessible. |
| 8. Restart the browser | Sample requirement: Remember me on preserves login; off requires authentication again. Check under a defined browser session-restore configuration. |
Vary user status, device, discount type, promo validity and minimum spend. The original sample uses an eight-row combination matrix; full pairwise coverage is not verified here.
| # | User | Device | Type | Status | Minimum spend |
|---|---|---|---|---|---|
| 1 | Guest | Desktop | Percent | Valid | Met |
| 2 | Guest | Mobile | Fixed | Valid | Not met |
| 3 | Logged in | Desktop | Fixed | Expired | Met |
| 4 | Logged in | Mobile | Percent | Expired | Not met |
| 5 | Guest | Desktop | Fixed | Valid | Met |
| 6 | Logged in | Mobile | Fixed | Valid | Met |
| 7 | Guest | Mobile | Percent | Expired | Met |
| 8 | Logged in | Desktop | Percent | Valid | Not met |
The correct discount applies once and totals recalculate according to the promotion rules.
No discount is applied. A specific error explains the rejection; totals remain unchanged.
Condensed coverage from the regression checklist. These are planned checks, not execution results.
Requirements examples, adapted from the two original mind maps.
Explore coverage, regression duration and defect resolution in the original interactive dashboard.
A guided look inside my Postman collection: how requests share data, what the assertions check, and how the scenario cleans up.
A local demo API for cars and brands
Choose a request to explore its checks.
Clone the separate Car_store repository ↗, open its folder, then run:
npm install npm start
The collection uses http://localhost:3001.
Download the E2E collection below. Import it into Postman and select an environment with baseUrl set to your local API URL. Run all seven requests in their original order using Collection Runner.
The scripts save generated values and IDs in the selected environment. The final two requests delete the created car and brand.
This page explains the collection; it does not send API requests or display a recorded test run.
A separate set of requests for cars, brands, reviews, filters, search, sorting and pagination. These are manual exploration examples; the exported collection does not include implemented assertion scripts.
Some requests use fixed IDs. Review the data and update IDs before sending requests, especially DELETE and database reset requests.
Six years at Astral Soft, growing from technical support into QA and helping teams make defects easier to understand and resolve.
Manual, API, backend and integration testing for B2B and B2C products. I validate data and access control with SQL, logs and API responses, investigate defects, and check fixes before release.
Introduced test-case reviews and coordinate QA-side automation priorities, regression scope and dependencies.
Led a technical support team of up to 20 people. Established a third-line defect triage workflow, with reproducibility checks and structured escalations to developers.
Investigated software issues using SQL, logs and Kibana for electronic signature and encryption products.
Get in touch to discuss my work and testing approach.