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.
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.
Typing full Cypress CLI commands every time gets old fast. Instead of this: npx cypress run --spec "cypress/e2e/firstTest.cy.js"npx cypress run --spec "cypress/e2e/firstTest.cy.js" --browser firefox Create reusable NPM scripts once — then just run: npm run cypress:smoke-firefox Cleaner. Faster. Better for CI. Why Use NPM Scripts? Avoid repeating long terminal commands Standardize execution across the team Simplify CI/CD pipelines Centralize configuration in one place (package
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
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