E2E tooling

Cypress

Cypress complements Playwright for scenarios where its developer experience and network stubbing shine—especially journey-style tests and rapid local debugging on the same codebase.

Why Cypress

Not every team runs both Cypress and Playwright; this portfolio documents both to show breadth. Cypress is strong for interactive demo pages and for validating UI against controlled API responses.

E2E workflow validation

Full user journeys through the SPA with readable specs and time-travel UI.

API interception

Stub or assert on network calls—useful for gateway responses and error simulations.

Debugging experience

Screenshots, video, and command log make local iteration fast.

Fast feedback loop

Interactive runner during development; headless runs in CI.

Sample coverage areas

  • User flows across demos
  • Navigation journeys
  • Route content validation
  • Demo interactions (forms, buttons, results)

Planned / implemented coverage

Cypress e2e specs under cypress/e2e/.

Cypress planned and implemented coverage by area
AreaStatus
Journeys: home → demos → projects
Implemented
Testing hub + return home
Implemented
Footer consistency (multi-page)
Implemented
Contact + LinkedIn regression
Implemented
Prod smoke (read-only)
Implemented
API intercept / error UI (planned extension)
Planned