The BlazeMeter Continuous Testing Platform is a unified, end-to-end, next-generation software test automation platform built for both Agile and COE teams, from Perforce. BlazeMeter includes complete continuous testing capabilities deeply integrated into a single, intuitive workflow.
$199
per month
Parasoft SOAtest
Score 4.8 out of 10
N/A
SOAtest, from Parasoft headquartered near Los Angeles, California, is a load and performance testing tool.
N/A
Visual Studio Test Professional
Score 7.0 out of 10
N/A
An add-on for the Visual Studio IDE, Visual Studio Test Professional subscription helps teams drive quality and speed. It includes test case management and collaboration features that streamline quality control and support continuous delivery.
$2,169
for the first year (renews at $869)
Pricing
BlazeMeter
Parasoft SOAtest
Visual Studio Test Professional
Editions & Modules
Basic
$149.00
per month
Pro
$649.00
per month
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
BlazeMeter
Parasoft SOAtest
Visual Studio Test Professional
Free Trial
No
No
No
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
BlazeMeter
Parasoft SOAtest
Visual Studio Test Professional
Features
BlazeMeter
Parasoft SOAtest
Visual Studio Test Professional
Automation Testing
Comparison of Automation Testing features of Product A and Product B
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.
This is the go to tool for all the web service testing needs. You can do functional testing, regression testing, automate the testing and drive the data from external sources like a Excel spread sheet or an xml document and finally performance testing. It can get better in scenarios where the response is to be compared with UI, with more automation. The license cost needs to be considered when there are many open source tools out there in the market.
It would be well suited if we used it with Azure DevOps as we can effortlessly integrate the test cases and even stories or tasks to stay on track with our work. Those test cases can even be reused across multiple projects. Using any other third-party tools, such as Jira, can be less appropriate, as it's not a Microsoft tool, and its capabilities will be limited.
Fast and efficient execution of automated testing.
Built in Javascript that can be used to run test cases with a repository tool such as HP Quality Center. This will show the test results and allow the QA engineer to pass, fail, or set a test case to N/A.
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.
As always, this is not a free tool and you have to pay for license. There are many open source tools which can perform similar job with no cost albeit with less functionality and more head work.
There is still some more room for improving the automation which can include more UI level components to make life lot easier when comparing the response vs UI.
The user community of the Visual Studio Test product is weak. For instant problems with this product, it is necessary to quickly reach the source of the error.
Licence fees need to be more reasonable. License prices need to be reduced so that they can easily compete with free testing tools.
It is very usable if you are familiar with Visual Studio to begin with. If you are new to the interface, it can be a long ramp up period for Testers not used to the GUI. There is always the web option which seems to be more intuitive for many Testers.
Visual Studio Test Professional is backed up by the full support of the Microsoft Corporation. That means twenty-four/seven customer support by quality, highly-trained professionals who understand every possible issue that you have experienced before. They are nice, efficient, and highly professional. I recommend them.
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.
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
It has been of tremendous help as the ONE STOP TOOL to test the APIs end to end. Ease of use is great and their support staff is excellent. They always conduct brown bag sessions for us to learn about new features. Overall it has given us a great ROI considering how fast we can test and deliver to market.
One of the positive ROIs of Visual Studios is the fact that it makes producing our work at a quick rate, things like Intellisense make our work get produced at a much higher rate which is good for our return of investment.
Testing by the developers has increased by 23%, we now take the time to actually test our product before we send it to our QA people.
I am not aware of any negative ROI aspects to our company that have been found.
