The App Has Changed, and All Tests Are Failing! How Do I Fix Them?

on YouTube ↗22m

" summary

A 26-test Cypress suite runs against a newer GitLab image and 22 of 26 tests fail; fixes follow a five-step loop: read headless logs, reproduce in interactive Cypress, inspect DOM and console, edit tests, rerun until green. Failures stem from changed selectors, moved URLs and removed features; practical techniques shown include cy.session and cy.request to speed setup and replacing brittle selectors with scoped queries using cy.get(...).find(...).first() to target the visible element and make results deterministic on CI.

AI-written summary · about

" chapters (7)

1. 0:00Why automated tests fail
2. 1:21Reasons for outdated tests
3. 3:59Demo project and optimization
4. 5:52Five-step debugging process
5. 7:45Practical debugging example
6. 12:31Iterative test fixing
7. 19:53Final tips and resources

" related talks

• 13mDon't Get Lost in the Trees: An Intro to CypressCJ Joulain · WFH Conf 2020
• 23mGaining Confidence with Cypress TestsRob Richardson · React Advanced 2021
• 47mEnd to End Testing with CypressAvindra Fernando · All Things Open 2020
• 46mAvoiding The Suck Of Testing Using Cypress.ioJoe Eames, Jesse Sanders · ng-conf 2019
• 57mGaining Confidence with Cypress TestsRob Richardson · NDC London 2021
• 35mCypress Tales: Effective E2E TestingNikola Đuza · Armada JS 2019
• 29mEnd-to-end Testing Is Hard - But It Doesn't Have to BeGleb Bahmutov · ReactiveConf 2018
• 45mCypress: Testing without Selenium, Part 1Gleb Bahmutov · Selenium Camp 2019