Cypress: Stress / load testing

Created on 28 Mar 2018 · 8Comments · Source: cypress-io/cypress

Desired behavior:

I'd like a --stress-test parameter which lets me re-run tests for a set number of hours, with a final report to indicate which tests are flaky and which are sturdy.

~~As an alternative, it'd be fine if your dashboard service would aggregate fails over time, allowing me to see which tests need more attention.~~

This feature is going to grow in importance to me personally as my test suite grows in size.

Operating System: Linux Mint 18.3
Cypress Version: Cypress 2.1.0
Browser Version: Electron

Edit by @jennifer-shehane: Moved Dashboard feedback to https://portal.productboard.com/cypress-io/1-cypress-dashboard

dashboard proposal 💡 feature

Source

EirikBirkeland

👍27

Most helpful comment

I would like to also suggest parallel execution during --load-test. Typically I use Gatling for load testing; but Cypress and Gatling do basically the same thing: load the UI, interact, confirm.

Being able to leverage Cypress to execute a series of user actions with (for example) 10 simulated users, would cover the need for Gatling.

Stretch goal: record and display TTFB, average page load time, load bytes, HTTP code responses and counts (200,404,500,etc).

davidjeddy on 10 Dec 2019

👍4

All 8 comments

I also wish to have this feature included in cypress. Similar features I saw elsewhere is: https://github.com/loadimpact/k6

jianentrinsik on 28 Mar 2018

This is a great idea. +1

cameronc56 on 2 Apr 2018

Related to test retries https://github.com/cypress-io/cypress/issues/1313

jennifer-shehane on 1 Mar 2019

In terms of the 'Test Count Aggregation' idea for the Dashboard - You can express interest and see progress for this feature on our Roadmap from our Dashboard's product board here: https://portal.productboard.com/cypress-io/1-cypress-dashboard

This issue will now be tracking all work related to 'Load Testing' - as this is a feature that would involve the Cypress Test Runner.

jennifer-shehane on 24 Oct 2019

👍1

@jennifer-shehane what issue on the dashboard would that be? I'm extremely interested knowing how I can use the tests to load test my app. I Would like to know more about what you are thinking

sturlath on 6 Dec 2019

👍1

I would like to also suggest parallel execution during --load-test. Typically I use Gatling for load testing; but Cypress and Gatling do basically the same thing: load the UI, interact, confirm.

Being able to leverage Cypress to execute a series of user actions with (for example) 10 simulated users, would cover the need for Gatling.

Stretch goal: record and display TTFB, average page load time, load bytes, HTTP code responses and counts (200,404,500,etc).

davidjeddy on 10 Dec 2019

👍4

Has anyone tried wiring up a Cypress test with Gatling? I am guessing that when Gatling forks threads, it wont be compatible with the reporting? I am thinking about it. Or did anyone have some other solution to performance test?

djangofan on 23 Sep 2020

Has anyone tried wiring up a Cypress test with Gatling? I am guessing that when Gatling forks threads, it wont be compatible with the reporting? I am thinking about it. Or did anyone have some other solution to performance test?

can someone answer this? it will be very helpful