TechValidate Research on Broadcom BlazeMeter

13 Charts


BlazeMeter Customer Research

How did you first encounter BlazeMeter?

Web Search: 43%
Provisioned by my company: 28%
BlazeMeter University: 7%
Event/workshop: 5%
Blog: 4%
Ads: 1%
Other: 12%

BlazeMeter Customer Research

Where do you go to learn new technologies and stay up to date?

Web search
77%
Take online courses - Udemy, BlazeMeter University, Test Automation University, LinkedIn Courses, etc.
66%
Expert blogs
47%
Ask peers
38%
News sites like DevOps.com, SDTimes, DZone, etc.
36%
Product documentation
31%
Social media (LinkedIn, Twitter, etc.)
25%

BlazeMeter Customer Research

When evaluating BlazeMeter, which other products did you consider?

Open Source Tools
72%
HPE LoadRunner/Performance Center
28%
Smartbear
28%
Tricentis - Flood.io
10%
Parasoft
7%

BlazeMeter Customer Research

Is your organization using or interested in using BlazeMeter’s Continuous Testing Platform capabilities? If so, which ones?

API test and monitoring
56%
What? I thought BlazeMeter was still just performance and load testing!
43%
Combined functional and UI testing (see what the user sees under load)
41%
Test data
21%
Mock services
19%

BlazeMeter Customer Research

Which of the following statements do you agree with?

It is easy to get started with BlazeMeter
84%
BlazeMeter offers us the ability to use open source with enterprise features and scale
63%
BlazeMeter delivers a great customer experience
54%
BlazeMeter offers great value for money
35%
BlazeMeter University has allowed me to get more value out of BlazeMeter
35%
BlazeMeter is designed for shift left testing
29%

BlazeMeter Customer Research

Which of the following statements do you agree with?

Our teams like using open source technologies.
75%
Continuous testing needs to be fully integrated into the CI/CD pipeline to be successful.
73%
It’s important to have API-driven testing (as code).
60%
Obtaining test data is a persistent problem.
31%
Traditional testing tools hold teams back from shifting left.
18%
Our dev teams all choose different tools in silos.
12%

BlazeMeter Customer Research

How much testing is currently done in the CI/CD pipeline (ie, in sprint, by the dev teams)?

Almost none (less than 10%): 10%
Very little (10%-25%): 19%
Some (25%-50%): 25%
A good amount (50%- 75%): 28%
All or Almost all (over 75%): 17%

BlazeMeter Customer Research

Is your organization focused on shifting testing left?

Yes, we are working on it actively.: 47%
We have talked about it, but we’re not “focused” on it.: 28%
We’re already fully shifted left. Most testing is done by developers and/or we no longer have traditional QA.: 10%
No, this isn’t a focus for us.: 15%

BlazeMeter Customer Research

Is your organization focused on shifting testing left?

Yes, we are working on it actively.: 47%
We have talked about it, but we’re not “focused” on it.: 28%
We’re already fully shifted left. Most testing is done by developers and/or we no longer have traditional QA.: 10%
No, this isn’t a focus for us.: 15%

BlazeMeter Customer Research

How long did it take you to begin testing with BlazeMeter?

Less than 1 day: 63%
Less than 1 week: 29%
More than 1 week: 8%

BlazeMeter Customer Research

What are some of the issues holding back your organization when using LoadRunner?

Need multiple tools for continuous testing
38%
Unable to test using existing open-source tools
34%
Manually creating/maintaining multiple scripts
28%
Testing is not keeping pace with software releases
21%
Too difficult to set up and use
17%
Inability to run performance tests across multiple geographical locations
15%
Long delays/restrictions when wanting to test
15%

BlazeMeter Customer Research

LoadRunner customers held back by having to manage multiple tools for continuous testing

Highlights what they want in an integrated continuous testing platform

Performance Testing
94%
API Testing
67%
UI Functional Testing
67%
User Experience Testing
50%
Scriptless Testing
44%
Mock Services Testing
39%
Test Data On-Demand
39%

BlazeMeter Customer Research

Key issues holding back organizations that’s using LoadRunner today.

Need multiple tools for continuous testing
40%
Unable to test using existing open-source tools
33%
Manually creating/maintaining multiple scripts
29%
Testing is not keeping pace with software releases
24%
Too difficult to set up and use
19%
Inability to run performance tests across multiple geographical locations
14%
Long delays/restrictions when wanting to test
14%



More Research on Broadcom BlazeMeter