In July, Amazon made available to its 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 - is built into the AWS CodePipeline continuous delivery flow, enabling users to test APIs, mobile and web applications easily and rapidly. Now, we are very excited to a guest post of BlazeMeter published today on the AWS Partner Network blog.
All about Continuous Testing, DevOps, JMeter, and more!
This post is part of our 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 previous posts we looked at a general overview of Taurus, and how to work with multiple tests. Here we demonstrate how easy the process is in Taurus to defining the desired throughput in requests per second.
When looking at a load test, many people choose to focus on the specific elements involved in that specific test, including the number of threads that should be used, response times and hits. This post, however, looks at the process itself - hopefully giving you a better chance for an effective and successful load test event.
In this next post in our series on Taurus, we look at overcoming the challenge of working with multiple test script files, with multiple engineers involved, when load testing complex applications. With the help of Taurus, combining several JMeter scripts into a single unified test is not only achievable but easy.
The question of when and how to use manual and automated testing in the application lifecycle usually has attracted much debate. In general, we follow our existing habits. Teams without a long history in automation are likely to support continued manual testing whenever feasible, while those with the tools and automation experience often attempt to automate everything. But Q/A teams and developers will tell you that the reality is more nuanced. You need both manual and automated testing. Each approach has its role at different times in the testing practice, and both contribute to the ability of a team to deliver high quality releases. The question is when to use one versus the other? Let’s take a closer look.
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.