BlazeMeter vs. Cypress.io vs. WebdriverIO

It is well suited for applications that are mission-critical or applications that can receive high traffic/transactions at unscheduled time periods. Using the load testing feature of BlazeMeter, we can test and ascertain the capacity of the application without the drawbacks of the usual Apache JMeter load testing which depends heavily on the host system from where the load testing is performed.

Incentivized

Everything web-based should be testable. Even our highly dynamic content-providing web application works well. Hopefully, it will get a bigger user base in the future so that one can find even more support at StackOverflow or similar forums.

Incentivized

Best suited where frontend developments are in React and where BDD and TDD test frameworks are to be used. Its syntax is very easy to write and understand. Even the non-programmer can do the initial setup. Not suited when the language you are using is other than Javascript(or Typescript).

Incentivized

• BlazeMeter takes the .jmx script that teams had written for JMeter. The transition from JMeter to BlazeMeter was seamless.
• BlazeMeter offers its own cloud and hence we did not have to set it up on-premise.
• BlazeMeter hits our application from various geographic locations that simulates real life users.

Incentivized

• Cypress automatically waits for DOM elements before interacting dev, this eliminates adding explicits waits in your code.
• Has built-in recording and debugging tool.
• Cypress has executions faster since you can update your code in the fly.
• Very easy to configure / setup

Incentivized

• numerous integrations to tools
• fast easy location of page elements
• tool setup is amazing - they have a script to walk you through everything with prompts!!

Incentivized

• Blazemeter reporting is very basic and shallow. There is no way to drill down or correlate. I can get better reports by using JMeter for free.
• Blazemeter is very costly. Testing with volumes of more than 1K cu is expensive, and can be done for much cheaper if a company/team is willing to invest a bit of time to figure out how to use cloud instances and jmeter slaves, and to write a basic script to collect resulting xml output.

Incentivized

• There are a lot of plugins but several of them have many errors. So Cypress.io should work integrating more features so that people should not rely on these plugins. For example, many people use cypress-cucumber-preprocessor and Cypress.io can start by integrating Gherkin support by default so that reliance in plugins are decreased.

Incentivized

• wdio.conf can contain too much where everything is encapsulated there, like the before and after functions
• A data provider-like testing would be useful. The only way to input different data into the same test is via a loop
• everything is needed to be done using the 'browser' object. Can be limiting where you don't have access to the browser depending on where you are in the code

Incentivized

Highly satisfied and [a] big fan.

Incentivized

Easy to setup to do API Performance Testing. Dashboard to showcase results Capability to showcase runtime results

Incentivized

In comparison with Blazemeter the closes competitor is JMeter but it has disadvantages like it is not a tool that can be use as a collaborative tool and works locally in a computer, Blazemeter is in the web so different people can access and run tests or collaborate do add, edit or delete the existent scripts.

Incentivized

Execution speed and interactive debugging tool is very easy. you can make changes in the fly and test will run automatically, thus saving more time debugging your code. Can easily be intergrated to to CI/CD pipeline

Incentivized

Other tools we selected don't work in our application, it does or doesn't support multiple frames or need more tweaking just to make it works. When testing out WebdriverIO it just works as expected, no need to do such walk around to make it works multiple frames. It also can handle multiple tabs and windows.

Incentivized

• It helped positively by helping to identify the maximum capacity needed for high traffic periods
• Saved revenue by eliminating unwanted duplication of systems

Incentivized

• Flaky tests can be caught easily
• Regration testing of application with Cypress.io helps to maintain quality of the software product.

Incentivized

• It helped in cross browser testing
• It helped in automating multiple browsers at a time.
• Code coverage is optimum as this supports Javascript(Typescript)

Incentivized