Quality Engineer

Fintech, Automotive & Trading Platforms

I catch bugs before they become problems.

Experienced

Test Automation Engineer

QA/QE/SDET | 10+ years | Front & Back End | Java | Ford, Aviva | Now at Create Future (FanDuel, Wood Mackenzie, Evoke) | London

Explore More

A Little About Me

I Love To Travel

Studying in the U.S. broadened my worldview and sparked a love for diversity and exploration. I’ve since lived in Michigan, Warsaw, and London—and traveled to 60+ countries.

Full-Stack Testing

My experience includes frontend testing of user interfaces and backend testing of services, data handling, and application logic.

Front End

Back End

Git Repositories

Mainly basic projects and practice work I can revisit or use as quick references. It’s a simple archive of things I’ve built and learned from.

Take A Look

Digital Shelf

It’s more of a personal collection—random things I come across, resources worth remembering, and thoughts I might want to come back to later. Just a place to keep track of it all.

Skip Login With Saved Token in Cypress

Typing email + password in every test is slow and noisy. Cypress can skip the login screen completely by grabbing a token via API and placing it into localStorage before the app loads . This is a practical reference showing the before vs after , plus a reusable custom command. Why This Helps UI login usually costs ~8 seconds per test run (open page, fill fields, submit, wait UI). Token-based login can cut it to ~5 seconds because it avoids the whole form flow. Tests become cl

E2E API Testing in Cypress

Cypress can run full end-to-end API workflows without opening the browser UI. It’s fast and stable, and it’s a good skill to understand. That said, for serious API testing at scale , Cypress is not the best tool. It works, but it gets clunky quickly. This post shows the approach and also explains where it makes sense (and where it doesn’t). What “E2E API Test” Means Here This type of test validates a full data lifecycle using only HTTP calls: Create auth token POST a new art

Test Data with API for Cypress Test

UI flows are great for end-to-end confidence, but they’re slow when used just to “prepare data”. A common Cypress pattern is: create the test data via API run the real scenario via UI validate the result in the UI (and optionally via API) This page is a reference for that workflow. Why cy.request() is Useful cy.request() sends HTTP calls directly to the backend. It’s perfect for: creating articles/users/orders fast avoiding flaky UI setup steps keeping tests focused on the th

View All