Summary

In this chapter, we have learned how Cypress enforces actionability for elements by ensuring that they are in the correct state before commands are performed on the elements. We learned that Cypress checks for visibility, disability, DOM detachment, readonly modes, animations, covering, scrolling, and element coordinates before it performs any action on an element. We also went through how Cypress calculates the animation of elements and even how it changes the coordinates when actions are being performed on elements. We also learned that it is possible to override the default checks that Cypress puts in place by forcing actionability in our tests.

Having completed this chapter, I believe you have the skills needed to understand how Cypress determines actionability for elements and also how we can override actionability in our tests to reduce complexity. In the next chapter, we will look at using variables and aliases, and we will dive into reusing variables and aliases...