Understand The Background Of Cypress In Test Automation | Infogen Labs
Let's Understand The Background Of Cypress In Test Automation | Infogen Labs

Understand The Background Of Cypress In Test Automation | Infogen Labs

Which problems we were facing with existing tools?

Previously we were looking into Selenium, though Selenium makes a website or web-app testing simple, there are a fair number of challenges in Selenium automation that developers face while using the framework. Let’s have a look at some of the most common challenges faced in Selenium Automation like False Positives & False Negatives (Flaky Tests), Waiting for Web Page with JavaScript To Load, Not So Scalable Approach, Handling Dynamic Content, Explicit Wait for Handling Dynamic Content, Implicit Wait for Handling Dynamic Content, Handling Pop-up Windows Switching Browser Windows, You Can’t Test for Mobile Devices, Generating Test Reports

?

Why did we start looking for new tool?

Cypress was written in JavaScript, which is the main language for our frontend developers team so it seemed like an obvious choice. This tool meets almost all of our expectations and even exceeds them in many cases. Cypress framework captures snapshots at the time of test execution. This allows QAs or developers to hover over a specific command in the Command Log to see exactly what happened at that particular step. One doesn’t need to add explicit or implicit wait commands in test scripts, unlike Selenium. Cypress waits automatically for commands and assertions. Developers or QAs can use Spies, Stubs, and Clocks to verify and control the behaviour of server responses, functions, or timers. The automatic scrolling operation ensures that an element is in view before performing any action (for example Clicking on a button). Earlier Cypress supported only Chrome testing. However, with recent updates, Cypress now provides support for Firefox and Edge browsers. As the programmer writes commands, Cypress executes them in real-time, providing visual feedback as they run.

?

What tools did we evaluate and what was the criteria?

Previously we had evaluated Selenium and Protractor tool for UI automation.

We had used following four major criteria for selection of testing tools like Meeting requirements, Technology expectations, Training / skills and Management aspects.

?

Why did we select Cypress?

We didn’t choose Cypress without a reason. This tool also has a lot of advantages as a test automation framework.

?It’s written in Javascript, based on Mocha and Chai, and runs in browser using Node.js . This makes it fast and reliable for testing almost every website, not only ones written in Javascript. So it would be a great choice if you want to test applications built in, for example latest React, Angular, Vue, Elm, etc. In Cypress the test code is executed inside the browser itself, so whatever language a website is built in it can be compiled to JavaScript. Unlike other testing frameworks, Cypress doesn’t run outside of the browser executing remote commands across the network. It uses the same run loop as your application instead. Using built-in Node.js server, it reads and modifies web traffic while operating on the network layer of tests running in browser.

With Cypress you can test literally anything that runs in a web browser. You can also implement Cypress tests to run on a mobile webview. The only limitation is the ability to test on Chrome browser. This could be a problem if you would like to test your applications with a wide range of browsers, but it can also be overcome by using additional tools, browser and device farms, etc.


Below are the major features that influenced our decision:

Cypress comes fully baked, batteries included. Here is a list of things it can do that no other testing framework can:

1.Time Travel: Cypress takes snapshots as your tests run. Hover over commands in the Command Log to see exactly what happened at each step.

2.Debuggability: Stop guessing why your tests are failing. Debug directly from familiar tools like Developer Tools. Our readable errors and stack traces make debugging lightning fast.

3.Automatic Waiting: Never add waits or sleeps to your tests. Cypress automatically waits for commands and assertions before moving on

4.Spies, Stubs, and Clocks: Verify and control the behaviour of functions, server responses, or timers. The same functionality you love from unit testing is right at your fingertips.

5.etwork Traffic Control: Easily control, stub, and test edge cases without involving your server. You can stub network traffic however you like.

6.Consistent Results: Our architecture doesn’t use Selenium or WebDriver. Say hello to fast, consistent and reliable tests that are flake-free.

7.Screenshots and Videos: View screenshots taken automatically on failure, or videos of your entire test suite when run from the CLI.

8.Cross browser Testing: Run tests within Firefox and Chrome-family browsers (including Edge and Electron) locally and optimally in a Continuous Integration pipeline.

?

After using cypress what did we find??

After using cypress tool, I have seen some measurable items such as Cypress is simple and fast to set up, it has the capability to debug and implement very faster, delivers quick test execution. It has an active group of people and combines functional testing with API inspection. It reduced script development time as well as reduced regression test time.

?

What types of tests this tool is Good?

Cypress enables you to write all types of tests:

1.End-to-end tests

2.Integration tests

3.Unit tests

4. API test

Cypress can test anything that runs in a browser.

?Visit Us:?corp.infogen-labs.com?

Business Enquiry:??[email protected]

要查看或添加评论,请登录

社区洞察

其他会员也浏览了