@alexhan
SDET
Nothing here yet.
Nothing here yet.
Mar 10 路 4 min read 路 When building End-to-End (E2E) test automation with Cypress, you'll inevitably run into one major issue: repetitive code. Whether it's logging in before every test or adding items to a cart to set up
Join discussionFeb 19 路 4 min read 路 ON THIS PAGE Why Do We Need cy.task? When Should You Use It? The Critical Difference: cy.task vs. Helper Functions Step-by-Step Implementation Guide Step 1: cypress.config.ts (The Backend Logic) Step 2: cypress/support/commands.ts (The Command ...
Join discussionFeb 10 路 3 min read 路 One of the most frustrating things about moving from local development to a CI/CD pipeline (like GitHub Actions, GitLab CI, or Jenkins) is debugging. You run your tests locally in the Cypress runner, and you see everything: cy.log() messages in the C...
Join discussionFeb 10 路 3 min read 路 As an SDET, we often rely on the standard npx cypress run command. It works great for running everything at once, but in the real world, things are rarely that simple. Sometimes you need to run tests in a specific sequence. Other times, you need to t...
Join discussion