Cypress is a frontend testing framework built on top of Mocha. It is used mostly for libraries like React.js, Vue.js, and Angular.js. For quality assurance personnels’ and frontend developers, Cypress is considered a top choice for end-to-end testing. Its non-reliance on Selenium makes it perfect for browser DOM elements.
However, Cypress has some major limitations that hinder it from being the standard framework for writing test scripts. This is the reason many other competitors have emerged in the market to solve these limitations of Cypress.
Some of these major limitations to Cypress which Developers found include:
Cypress is Slower – Contrary to popular beliefs and the documentation from the Cypress team which claims Cypress is faster than most automation tools out there, it is slow. Its execution speeds at the stage of initiation and project launch are fast but as the application grows and develops, Cypress becomes very slow as it can’t keep track of all the progressive changes. This makes it inefficient and difficult to maintain test automation.
Maintenance – As with most applications, the process of the Software Development Life Cycle is an ever-growing one. The application grows as more features and functionalities are added and in turn, so are test suites and test cases. Developers have found it difficult to keep up with these changes while using Cypress for testing. Tests are scheduled to happen rapidly and, in most cases, Cypress can’t keep up.
Cypress downfalls and why people search for alternatives