Protractor app code#

You don't need to do things like switch between tabs or test links to external top-level domains

Protractor app code#

You're at a smaller company and have a close relationship with developers who can help write hooks or stubs in their code to assist your testing Not everyone knows about this type of thing, so it's common to find Selenium frameworks that are set up poorly. For example, a hub/node configuration where the selenium jar is on a different physical machine than the browser under test will cause unreliability in your tests. Harder to set up, and the method of setup impacts its reliability. Therefore it is a bit harder to read the code. Less graceful handling of promises - relies on async/await or. Slower and more brittle - in general there is a higher likelihood of cryptic and/or intermittent errors which may cause your tests to fail even though there is nothing wrong with your applicationįor highly experienced automation engineers, the fundamental 'brittle' nature of Selenium can be worked around - it can be reliable but only if you really know what you are doing More extensive community support and documentation More powerful because it is Selenium-based - it can switch between tabs, it can handle external links to other domains, it can handle iFrames, simulate keypresses and clicks, and move the mouse to specific co-ordinates within the browser. Sometimes has trouble switching between different top-level domains, so not good for testing external linksĬypress is a newer tool with less extensive documentation and less community support

More reliable (tends to throw fewer intermittent false failures)Įasier to read code (handles promises gracefully)Ĭannot specify clicks or keypresses explicitly as if a real user was interactingĬannot move the mouse to specific co-ordinates Here are some advantages and disadvantages of each tool:

Your choice of tool should depend on your specific testing needs. Cypress is the easier and more reliable tool, whereas Protractor is the more powerful tool. I've used both Protractor and Cypress extensively.

Here's a link to Protractor's open source repository on GitHub.Īccording to the StackShare community, Cypress has a broader approval, being mentioned in 59 company stacks & 44 developers stacks compared to Protractor, which is listed in 24 company stacks and 22 developer stacks. Protractor is an open source tool with 8.24K GitHub stars and 2.23K GitHub forks. 'Open source' is the top reason why over 4 developers like Cypress, while over 2 developers mention 'Quick tests implementation' as the leading cause for choosing Protractor. Protractor runs tests against your application running in a real browser, interacting with it as a user would.Ĭypress and Protractor belong to 'Javascript Testing Framework' category of the tech stack. Protractor is an end-to-end test framework for Angular and AngularJS applications. On the other hand, Protractor is detailed as ' End-to-end test framework for Angular and AngularJS applications'. Cypress works on any front-end framework or website. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. Cypress is a front end automated testing application created for the modern web. Cypress vs Protractor: What are the differences?ĭevelopers describe Cypress as ' Better, faster, and more reliable testing for anything that runs in a browser'.