Why documentation is overrated in Agile Performance Testing
Introduction Once upon a time documentation was one of the most important aspects of Quality Assurance and this was not limited to the functional test efforts but the non-functional testing as well.
We spent days, weeks, months even creating Performance Test Strategies, Approaches, Plans, Test Case, Completion Reports etc.
Most of these documents were required before any automation could be written and before a sensible performance testing framework could be considered.
Exploring the hidden benefits of repurposing performance testing scripts.
Introduction If you are a performance testing specialist or a QA Manager or Programme Manager or anyone involved in the production of quality software then you understand why performance testing is required and its benefits in ensuring your products meet your Quality Criteria for release into production.
The costs of delivering performance testing are easily worth the investment as software that performs not only ensures you and your company have a reputation for delivering well performing software but business users will, in my opinion, overlook and embrace small functional workarounds if the software performs well.
Simple way for creating complex business scenarios in JMeter using Groovy scripts and the JMeter Switch Controller.
Introduction Creating complex performance testing scenarios in JMeter can be a complicated but necessary problem you will encounter as you build tests to mirror real user behaviour in your testing.
There are many add-ins that can support you in the creation of these scenarios. Which is good if they do what you want them to do. But if you want the flexibility to build tests without the limitations of 3rd party add-ins then there are several techniques you can use which come with the standard JMeter install.
Introduction The Beanshell Interpreter in JMeter can act as a server which as stated in the JMeter documentation is accessible by telnet or http.
So what, I hear you say, well this can be useful and we will explore some of these uses in this Blog Post.
Before we move on the definition of a Beanshell can be found on the official Web Site.
But at a high level:
You can use BeanShell interactively for Java experimentation and debugging as well as to extend your applications in new ways.
How to create realistic (and meaningful) load tests by parameterizing Gatling scripts using feeders and regular expression extractors.
This blog post is a tutorial for writing Gatling scripts to load test web applications. It follows our first getting started with Gatling simulation scripts article.
The application under test is a fake e-commerce. We are going to create a Virtual User that browses articles in this shop. To create a dynamic load test we will cover several topics:
Feeders to inject values taken from a static file, Regular Expression extractors to extract value(s) from a server response and inject it in subsequent requests, Cookies management.
Getting started with Gatling simulation scripts. This tutorial explains everything you need to know in order to run your first load test with Gatling.
Gatling is a load testing tool for measuring the performance of web applications. As such, it supports the following protocols:
HTTP, WebSockets, Server-sent events. Other protocols are also supported either by Gatling itself (like JMS) or by community plugins.
Gatling load testing scenarios are defined in code, more specifically using a specific DSL. This guide focuses on the basics of writing a simulation to test an HTTP application: OctoPerf’s sample PetStore.
OctoPerf 11.6 is available, with new automatic SLAs, improved administration for enterprise customers and increased usability with many small quality of life features
Improvements JMeter 5.2.1 In december, we updated OctoPerf to use the latest JMeter version. Although, as a minor version, it doesn’t bring a lot of new features, it is always better to stay up to date with the latest bugfixes. We had to implement a small change in OctoPerf because JMeter now properly enforces the cache control headers in every situation. To avoid any confusion, cache control headers have now been disabled by default in OctoPerf:
Kraken 2.0 release notes: multi-injectors load testing and features list. Video tutorials. Roadmap for the upcoming releases.
Kraken is a load testing IDE based on Gatling.
As such, Kraken provides a complete development environment to software programmers and load testers that seek to make the most out of Gatling:
A code editor to create and update .scala Gatling simulations with autocomplete suggestions and code snippets, Simulations debugging and comparison with HAR imports, Load tests analysis with aggregated data in InfluxDb displayed in comprehensive reports generated with Grafana.
Making sure your performance testing execution strategy is suitable.
Introduction When we consider performance testing most of the focus of the approach is placed on the script creation activity and making sure that requirements are covered, these are very important parts of your performance testing approach but so is the Test Execution.
The frequency at which you run your tests is important and can save you time and effort in your script maintenance.
A good performance testing execution strategy gives you the maximum amount of benefit it can by finding performance issues early.
OctoPerf 11 is available, with modular design, tagging and improved user administration for our Enterprise customers.
Improvements Modular design One of the things we always wanted to handle in OctoPerf is modular design. In JMeter you can use test fragments. So far when you imported fragments in OctoPerf their content was just duplicated over the original Include controller or Module controller.
But now not only can you import your modular design from JMeter but you can also create it directly in OctoPerf: A fragment virtual user can be seen as a library of functions.