Skip to main content

Cypress (yet another) Selenium WebDriver killer

There is no perfect tool, there are tools which satisfy specific requirements and Cypress is one such tool. I have not used Cypress and my assessment on this post is limited to information I have gathered reading about Cypress. Cypress appeared to me Selenium Remote Control (aka Selenium 1) repackaged with Chrome browser at it target. Cypress target audience is different than of Selenium's, let's see what requirements they cater to.

Cypress target audience seems to be front-end developer. Its power lies in being able to test front end without having real back end or a mocked backend. Selenium's power lies in its integration capability with various other tools and APIs. Imagine testing on staging system which requires java based API to be invoked to create customer account following which using WebDriver to login to frontend and creating a transaction following which data base assertion to verify transaction attributes. Not all of these operations can be carried out using selenium however Selenium's vast support of languages makes all of these operations possible in selenium bases test suite.

Cypress focus area is Chrome. Given that we are past IE7 era, running tests on Chrome (or FF or modern IE) means that most of the time having a feature work on one browser would most likely mean that it works on other browsers too. Selenium's Support of multi-browser has also resulted in Bane. In theory Selenium tests are written once and run on any browser in practice Selenium tests are written once and debugged on any browser. The question we need to ask ourselves is that do we really want to run tests on gazillion of browsers.

What Cypress does not get right. Automation tool should be non intrusive in nature that is it should not change state of application to be able to work with it. You want to test the same application what your customers use and not a modified version of it. Unlike Selenium which uses browser automation APIs to carryout operation on browser, Cypress injects a js file to be able to execute test code. This intrusive nature of tool goes against principles of software testing.

Cypress solves very specific problem set in area of test automation although these problems can also be addressed by Selenium. In the end it is up to us which tool set we want to use to cater our requirements.


Comments

Popular posts from this blog

Using chrome console to test xPath and css selectors

Note: If you are new to java and selenium then start with selenium java training videos .       Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously wri

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos .     Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred