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.
Looking at ways of managing test data to support performance testing. From general principles to a complete example.
Introduction We are going to talk about data in this blog post, predominately test data required for performance testing.
This is something that makes the life of a performance tester extremely difficult and awkward as because of the huge quantities required, in the right state, that match the criteria required for your test to run.
We often have to approach the use of large quantities data for the purpose of performance testing in a number of ways:
Non-Functional requirements, what are they, how to define them and how to test them
Introduction What are they?
Well, non-functional requirements are requirements that define the operation of the system under test rather than the behaviour of the system under test, or the functional requirements as these are known.
The categories under which non-functional requirements are grouped are numerous with a degree of overlap, we are going to attempt to demystify some of these whilst attempting to articulate how they can be tested and some of the common pitfalls.
The subject of this post is a look at whether JMeter is a good alternative to LoadRunner. In-depth comparison oh both load testing solutions.
The subject of this post is ‘Is JMeter, a good alternative to LoadRunner’.
The short answer is yes absolutely, the longer answer is of course a lot more complex and interesting and worthy of discussion.
We will not discuss the more technical aspects of the tools as there are many, many posts talk about this already and it’s not worth repeating the same thing again.
Let’s look at it from a usability in the real world perspective.
Use Advanced logic in your scripts with JMeter If Controller. Design Dynamic JMeter Thread Groups thanks to this logic action.
You may ask yourself:
How can I script Thread groups with dynamic behavior? How to use the JMeter If Controller to leverage conditional behavior? Good News! We’re going to show you the JMeter If Controller by introducing you to conditional statements, advanced conditions and performance considerations.
Use-Cases The If Controller works great when you need to execute some elements of the Thread Group based on a given state.
A look at how we can build a performance test strategy for the agile world. From an open-source tool choosing to a working example!
A long time ago, Quality Assurance was executed after development. Performance testing was an activity executed when software was ready for production.
If a performance issue was found, most companies:
Fix the issue which means a complete new cycle including QA Tests and performance tests are required, Or put the software live and decided to fix it as part of ongoing development, Or borrow from the future. That’s technical debt.
A look at how we can build a complex soak test using BeanShell Samplers.
As performance testers Soak Testing is a test that is often overlooked.
We always think of Peak Volume tests and we always like to push the system to its limits in the form of a Scalability Test but often the Soak Test is forgotten about.
It’s a great test and it tells you many critical aspects about your application under load, things that no other test can and is critical in determining if you application is fit for production.
An in-depth look at the benefits of using JMeter properties to create configurable test plans.
Your company probably runs JMeter test plans on a regular basis. Tests constantly need to be adjusted to change settings like concurrent users or test duration. Editing the JMX is time consuming and error prone.
It’s painful, especially if you run test using Continuous Integration as part of a Shift-Left strategy. Thankfully, there is a way!
Let me guide you through all the options to design flexible JMeter test plans using configurable properties.
Learn the secrets used by best performance engineers to Debug JMeter including logs, variables, Regular expressions, JsonPath extractors and more.
If you ever have designed JMeter scripts, I bet you have been stuck at least one time figuring out why a Json Extractor is not working. Guess what? I’ve been there!
Do you know why best JMeter Performance Engineers almost always find solutions to their problems? They master JMeter Script Debugging.
That’s why I have compiled the best JMeter Debug Practices into a huge single post covering:
How to use the Debug Sampler (and get the best out of it), Leverage View Results Tree secret features: Regex Tester, Json Path Tester and Regex Tester (and never fail a variable correlation again), How to use Dummy Sampler to generate fake requests to try things (without hitting a real server!
Learn how to use the JMeter built-in http(s) recorder to record HTTP and HTTPS traffic directly from a web browser (like Firefox or Chrome).
So you started designing a scenario using JMeter manually. After working a while on this grueling task, you start wondering: Isn’t there a way to record browser interactions with JMeter?
The short answer is yes! Jmeter’s HTTP(s) Test Script Recorder is exactly designed to record test scenarios.
This tutorial teaches you:
What a Proxy is and how the recorder works, How to intercept and record HTTP Requests automatically while using your web browser, How to record SSL-secured (https requests), How to configure Proxy Settings with Google Chrome and Firefox, And the most important part: recording the script!