Test Before Merge: Cypress + Shipyard
summary
Argues that running Cypress end-to-end tests on every PR using Shipyard ephemeral environments and a GitHub Actions workflow removes staging bottlenecks: CI builds a per-branch full-stack environment (Venmo clone demo), runs unit/integration/end-to-end tests on every commit, re-runs after fixes, and shuts the env down on merge. Claims users move from running tests twice a day to 5× per hour and eliminate about 42% of their E2E suite by catching flaky or redundant tests earlier.
AI-written summary · about
chapters (6)
- 0:00Introduction to E2E testing
- 1:22Challenges in current CI/CD
- 2:55The benefits of early testing
- 5:52The role of ephemeral environments
- 9:48Demo: Cypress and Shipyard
- 19:33Conclusion and Q&A
related talks
24mFast E2E Testing Using Cypress For Free
22mIncreasing our test stability and reliability with Cypress
50mShip Web Apps Confidently: End-to-End Testing with Cypress
35mCypress Tales: Effective E2E Testing
47mEnd to End Testing with Cypress
29mEnd-to-end Testing Is Hard - But It Doesn't Have to Be
26mTales from the QA crypt
32mCypress.io – the State of the Art End-to-end Testing Tool