BlazeMeter vs. MuukTest vs. OpenText UFT One

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

UFT is well suited if the price is not an issue, and if the requirement is about testing different technologies. If the application is based on Legacy platforms like Siebel or Mainframe, UFT fares quite well. For low cost web-based projects, there are other cheap and open source tools available. If it is about API testing or Mobile Testing, it is better to use other tools like TOSCA.

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

• The simple front end will allow novice users to easily grasp the basics of automation and give them confidence to try things for themselves.
• UFT can scale up and run across multiple machines from a single controller, such as ALM, enabling hundreds of tests to be executed overnight.
• There is an active support community out there, both official HPE based and independent users. This means if you do encounter a problem there is always someone out there to help you.
• The later versions have many add-ins to plug in to other tools within the QA world.
• Expert users are able to utilise the many native functions and also build their own to get the most out of the tool and impress people as they walk past and see the magic happening on the screen.
• UFT also has LeanFT bundled with it, allowing automated testing at the api level - if you can convince the developers to let you in there.

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

• Its licensing cost is very high making it a very expensive tool. due to this many organisations are exploring options of license free tools like Selenium for automation. Though learning curve is large in case of Selenium but it is very cost effective & you an get lot of support online for Selenium.
• Though the scripting time is less since its easy to create automation scripts, the execution time is relatively higher as it takes the lot of CPU & RAM.
• Though UFT is quite stable but during long execution cycles we do get frequent browser crashing issues.
• In terms of costing TestComplete is also one option which is not free but comes with modular pricing. You can buy what you need, when you need.

Incentivized

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

Incentivized

The ui is clean but there are lots of setting snd options which one must be fully aware so it will aid him/her during scripting

Incentivized

HPE are quick to reply and it's possible to get through to the actual developers shuold the case warrent it. Their online system allows updates and tracking of all incedents raised.

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

1. It works solid for automate SAP and S/4 Hana applications and Fiori too. 2. Teams are well versed about UFT One 3. Able to handle maintained execution results 4. Publish Automation execution results in well manner to the leadership team/stake holders 5. More help content available 6. Able to understand non technical resources about normal view.

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

• Reduces the total workload of keeping the team to test older (regression) functionality. QA testers can concentrate on ad-hoc and exploratory testing, saving time and effort across the entire project.
• Has built a better infrastructure for the client applications on which we can rely on for stability and providing regression results for any new features being developed.
• Led the applications a step closer to implementing agile practices and DevOps across the entire organization. Thus, providing a better turnaround time of new features to the customers and less maintenance headaches for the BAU team to address.

Incentivized