The Story of How We Moved from Geb to Cypress
summary
Allegro engineers describe migrating their service’s acceptance tests from Geb to Cypress.js to improve stability and reliability. The talk explains why they chose Cypress.js and shares the conclusions and lessons learned from the rewrite.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:31About the speaker
- 4:15Allegro scale
- 6:44Geb vs Cypress
- 12:09Project context: Orders tab
- 14:20Geb problems: Data and stability
- 18:33Geb problems: Non-intuitive exceptions
- 21:00Geb problems: Test execution time
- 23:30Geb problems: Project config
- 25:13Cypress fixes: API mocking
- 28:04Cypress fixes: Clear errors
- 30:55Cypress benefits: Dev and debug
- 33:01Cypress benefits: Setup and runs
- 34:31Summary and future plans
- 37:43Future: Critical tests and browsers
- 38:45Migration summary and takeaways
- 40:53Cypress demo
- 41:15Q&A
related talks
22mIncreasing our test stability and reliability with Cypress
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
59mCypress.io
35mCypress Tales: Effective E2E Testing
24mStrategy & Success with Adopting Cypress Component Testing
52mCypress: Testing without Selenium, Part 2
55mCypress: Hype and Reality
13mDon't Get Lost in the Trees: An Intro to Cypress