Introduction Regression Testing, as all Quality Assurance professionals know, is ensuring that previously developed and tested software continues to operate after a change.
Performance Regression being a subset of regression testing as a discipline is therefore ensuring that previously developed and tested continues to meet its performance criteria after a change.
There are subtle differences in the way that performance regression testing is approached when compared with functional regression testing and we will look to explore these in this Blog Post.
Overview of performance testing Kafka with JMeter. How to publish messages onto a Kafka topic?
Introduction This post is about Kafka and the process I have been through recently writing a performance test for an application that subscribes to messages from this technology.
The test I ended up with was in the end very straightforward but there were several hurdles that took a while to resolve. I hope that reading this post will hopefully help you avoid them.
The performance testing concepts we will discuss are focused on how to publish messages onto a Kafka topic and will not discuss how to write a test to consume messages from Kafka.
OctoPerf v12 is available, with our brand new scheduler and slack integration for your test notifications. We’ve also reworked the menus for a better navigation, and added a lot of smaller features.
Introduction It’s been some time since our latest major release, in fact OctoPerf v12 is probably our biggest/longest coming release to date. There’s of course been a couple of minor versions this summer and we’ll also cover them but first let’s focus on the new killer features: the scheduler, alerting through slack/mail and a better UI for the menus.
The scheduler is the first item left on our original roadmap (back when OctoPerf was still called jellly.
Is JMeter old technology or is it still suitable for modern day challenges?
Introduction “JMeter is old technology”, I hear this a lot.
“Let’s use this tool or that tool instead of JMeter as it’s the latest”, I hear this a lot.
“We need a lightweight tool without the GUI interface to write our tests as that will make us more agile”, I hear this a lot.
It’s all nonsense it really is, there seems to always be a call for using the most modern technology for all forms of testing whether its Performance Testing or Automated Functional Testing and the result of this is that the people writing the tests spend to long learning the new tools and not enough time building something that will ensure the software being developed is the best it can be.
Overview of JMeter plugins and how they can be used
Introduction JMeter in its vanilla form is a very powerful tool for performance testing, the ability to create complicated test scenarios using the out-of-the box samplers, timers and logic controller can sometimes be extremely difficult and require you to write your own complimentary code.
There are however Plugin’s that exist that can help in building some of the more challenging scenarios.
In this post we are going to look at some of these and discuss how they can be used.
How to send an HTTP POST request using Gatling and how to create modular scripts to reuse chunks of load testing virtual users?
This article is the fourth part of a series of tutorials dedicated to Gatling Load Testing.
Kraken is used to ease the debugging of Gatling simulations and to speed up the process of load testing a fake e-commerce website: PetStore.
We will focuse on POST requests and script modularization:
In the previous blog post we created a realistic Virtual User that browses the store without buying anything. On the contrary, here we are going to simulate the behavior of a user that connects to the web store, searches for items, adds some to his cart and proceeds to the checkout.
Overview of statistical techniques for results gennerated using JMeter
Introduction What does statistical analysis have to do with performance testing you may ask, more than you would think is the answer.
Due to the large volumes of result data that is generated and analysed you are performing statistical analysis of your data when presenting your results.
90th Line, 95th Line, 99th Line, Average, Median. Are all examples of values in the JMeter Aggregate Report.
Average, Std.Dev. Are examples of values in the JMeter Summary Report as well as the Graph Results.
How to replace Angular Material CdkTree (FlatTreeControl) by a CdkVirtualScroll loop? This blog post is a complete step by step guide.
While developing Kraken’s frontend I quickly stumbled upon performance issues with Angular Material tree when too many nodes where opened. Kraken is an open source load testing IDE. As such, it displays a tree of directories and files used to script the load testing scenarios:
You can have a look by creating a free account on the demo or check the source code of the UI on GitHub. It uses the latest version of Angular and components provided by Angular Material such as the tree.
Kraken 3.0: a new step towards an Enterprise grade solution. Users management with KeyCloak, Online Demo SaaS, Administration improvements.
This third version of Kraken represents one more step towards a load testing solution suitable to teams and enterprises. Kraken can already be installed on your own Kubernetes cluster thanks to Helm charts: You own all data and can handle the security inhouse.
But until now it was lacking users management, making it cumbersome to use it for a team of performance testers. This point is now addressed in the version 3.
Using Test Fragments, Module Controllers and Include Controllers in JMeter
Introduction The key to all good automation is modularisation which is effectively isolating small chunks of your application under test into separate tests and then re-using these smaller chunks in your larger, more complicated tests.
Example of good candidates for modularisation are logon and logoff as well as any other high-volume journeys through your application such as search functionality.
The rationale for this approach is that if these high volume common functional activities change you only need to make the update in a single test rather than in multiple tests.