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.
Tags help organize and filter tests so you can run only what you need. Examples: smoke regression api auth critical mobile Unlike some frameworks, Cypress does not have built-in tagging. Instead, it recommends using the @cypress/grep plugin. Installing tag support Registering the plugin In cypress/support/e2e.js: Tagging tests Tag a suite Tag individual tests Running tests by tag Run only smoke tests: Run only auth tests: You can also filter by test titles using grep. NPM scr
One of the most useful features in larger Cypress test suites is cy.session(). It helps solve a common problem: repeating the same setup steps, especially logging in before each test. cy.session() lets Cypress save and reuse session data like cookies, localStorage, and sessionStorage. This means you don’t have to log in every time. Cypress can quickly restore the same browser state. It also works with Cypress test isolation and can reuse sessions across different spec files
Precondition Install Docker Desktop: https://www.docker.com/products/docker-desktop/ Example setup: Core Idea Image = instructions (what to install + what to run) Container = running version of image Flow: Cypress Docker images: https://github.com/cypress-io/cypress-docker-images Dockerfile .dockerignore package.json docker-compose.yml Commands (minimal reference) Build image Run container Using docker-compose (recommended) When to Rebuild Rebuild if you change: Dockerfile pa