All about Continuous Testing, DevOps, JMeter, and more!
This post is part of a continuing series on Taurus, an open source test automation tool that extends and abstracts JMeter, and helps to overcome various challenges. Taurus provides a simple way to create, run and analyze performance tests. In the first post, we looked at an overview of what Taurus is, the installation process and some usage scenarios. Here we will look at some of the first steps.
With BlazeMeter, you could always run performance tests for your APIs, mobile and web applications easily and rapidly, and now the product brings you even more value with some cool new features. We recently held a webinar to explore these, as well as lesser known tried and true advanced features that will help you be a better tester.
As many of you know, JMeter is an open-source project created by Apache that serves as a load testing tool for analyzing and measuring the performance of a variety of services, with a focus on web applications. But for people who are new to JMeter, and even veteran users looking to revisit it from a big picture perspective, it's beneficial to have one source to find the best websites, blog posts, videos and tutorials that cover JMeter and best usage practices.
When it comes to performance testing, JMeter is fantastic...but not perfect. Automation and integration with other systems can be a pain, and the tool itself comes with a steep learning curve. In this post, we'll take a look at Taurus, an open source test automation tool that extends and abstracts JMeter, and helps to overcome these challenges. Taurus provides a simple way to create, run and analyze performance tests.
Today, Amazon Web Services (AWS) officially made available to customers AWS CodePipeline, a continuous delivery and release automation service. And as part of the platform, performance testing powered by BlazeMeter - a member of the AWS Partner Network and the go-to-choice for load and performance testing - is built into the AWS CodePipeline continuous delivery flow, enabling users to test APIs, mobile and web applications easily and rapidly. This post will look at what AWS Pipeline is, and 3 important ways DevOps engineers can utilize it to maximum benefit.
Discovering performance problems as early as possible would save you time and money. How about finding them out right after a commit? What about changing environment settings? How could you be sure that all 20+ nodes of your application are healthy running your changes? Some manual testing or one-thread automated testing simply wouldn’t do it. How about generating some smoke load?
The purpose of all “Timer” test elements is pausing a JMeter Thread representing a virtual user for a certain amount of time. The main goal of using timers is simulating a virtual user’s “think time”. In the world of load testing, “think time” stands for simulating real user behavior which causes people to wait between interactions with a web application. Let's walk through all available timers and explain what each of them does so it would be easier for you to choose the most appropriate one.
When it comes to building an advanced JMeter test plan, you can encounter the requirement to run certain samplers with a certain probability. In this post, we’ll guide you through the options on configuring weighted load and highlight options provided by JMeter.
JMeter is the undisputed leading open source testing tool. Yet challenges remain.