A Cypress test runs as fast as your application does. As soon as the command succeeds, the test moves on to the next command. This could create a dizzy blur of clicks, typed text, and page transitions. I wrote the plugin cypress-slow-down to delay every command by N milliseconds automatically so you can observe what happens in the test. Follow today’s lesson “Lesson b1: Slow down the test commands using cypress-slow-down” to learn how to use this plugin in your projects
The plugin can slow down the entire test or just its parts, but that will have to wait until another lesson and another Advent Day.
Previous lessons
Lessons marked with 📡 are from the Cypress Network Testing Exercises course. Lessons marked with 🔌 are from the Cypress Plugins course.
Day 1: 📡 “Spec 08: Import the JSON fixture directly into the spec”
Day 2: 📡 “Spec 14: Reloads the page until it sees the word Bananas"Cypress
Day 3: 🔌 “Lesson a3: Log the messages from the test to the terminal“
Day 4: 📡 “Spec 04: The application is showing the loading element“
Day 5: 📡 “Spec 11: Test how the application makes a network request every minute”
Day 6: 🔌 “Lesson a7: Re-run the tests when the source files change with cypress-watch-and-reload plugin“
Day 7: 📡 “Spec 16: Get the fruits from the test using the cy.request command“
Day 8: 📡 “Spec 19: Intercept a specific request by matching the header”