BlazeMeter is the leader in continuous performance testing for the continuous delivery era. They ensure the delivery of high- performance software by enabling DevOps teams to quickly and easily run open-source based performance tests against any mobile app, website or API on massive scale to validate performance at every stage of software delivery.
1. Please tell us about yourself. Name two interesting things about you that people might not know
My name is Iddo Greenberg and I am the R&D Director for the Platform Engineering team at BlazeMeter. My team is responsible for BlazeMeter’s backend and operations.
I have been in the Tech industry for 18 years. Most of my career has been in the financial technology domain and the algo-trading field.
On a personal note, I am married and have three kids, I like to cook and I build robots during my spare time.
2. Can you tell us a little about Blazemeter? How are you different and what makes you great?
BlazeMeter is a great company with a skillful team. I am proud to say we are the leaders in continuous performance testing, and this is a time where continuous delivery is everything. Our product ensures the delivery of high-performance software. This means that DevOps teams can run open-source based performance tests for any mobile app, website or API on a massive scale, really quickly. They can also validate performance at every stage of software delivery.
BlazeMeter integrates with many popular tools, like JMeter, Gatling, Grinder and Locust. This makes it easy for developers to take advantage of our product, but they can still use the tools they are used to. We have also developed strategic partnerships with some of the biggest names in the industry, like CloudBees, New Relic, AppDynamics, Dynatrace, Abstracta, Amazon Web Services, and IBM BlueMix.
Our head offices are located in Palo Alto, San Francisco and Tel Aviv. We have a large variety of clients from all over the world, ranging from independent developers to enterprises.
I think it’s also worth noting that our product generated revenue from the very first day of its operations, and that we are very affordable.
3. What are three main things that I am missing if I am not using your solution today? How could my life be better?
First of all we need to make sure you are load testing. If you aren’t, you should probably start as soon as possible, because load and performance testing ensure your app, website or API function properly at scale.
You’re probably familiar with JMeter, which is the most common tool for performance testing. JMeter is an open source tool, so you can start writing your tests on your personal laptop and run them locally. There are also many more OS tools that run locally, like Gatling and Locust.
This is where BlazeMeter comes in, either after using these tools or unconnected and independently from them:
First off, BlazeMeter is scalable. We can take your scripts, just as they are written, and run them from over twenty geographical locations worldwide.
Secondly, BlazeMeter reports can be viewed in real time. Think how amazing that is – you can see how your app behaves, where it breaks, and you can tweak your object under test LIVE. We also offer many types of reporting that you can choose from.
We integrate with Atlasssian and Jenkins. This allows you to take your tests and run them as part of the continuous integration cycle. We are very proud of this ability.
Finally, mobile testing: we offer a nice tool called the “recorder” which allows you to record operations from mobile device and create scripts based on these recordings. You don’t have to open the application itself. You just need to setup the proxy server address, that we provide, on your mobile phone, and we record the scenario.
It’s also important to mention that BlazeMeter doesn’t lock its users. Rather, you can use any open source tool you like, write scripts and then use us on demand and when you need it.
4. How do you see the testing and development ecosystems evolving in 3 or 5 years from now?
Everything is definitely “Shifting Left”, as agile methodology has taught us to give feedback earlier in the development cycle and the product release cycle. But since the proprietary tools of the past have not evolved with this changing workflow, they are becoming obsolete.
The problem nowadays is that the test environment is fragmented, which hurts productivity. In the future, modern software delivery will include load testing across all stages, for Developers, DevOps, QA and Ops; and for every new code, build and deployment. The development state of mind will be concentrated on detecting performance-related problems, as they happen, as part of the continuous delivery approach.
The Internet of Things (IoT) is also gaining serious momentum. From the Service Developer’s point of view, this means a different type of load in terms of distribution, size and quantity. The load testing industry should prepare toward loading this specific type of flows.
Source: QA Intelligence blog