Skip to content

Load Testing Blog

Soap Requests in JMeter

We are going to look at how to test SOAP Services using JMeter and some of the issues that you can face when testing these services.

We are going to provide some basic principles of SOAP in this post and while some requests can be complex in their definition and structure testing them is relatively straightforward.

The best approach to performance testing SOAP Requests is to discuss what the structure of the message is with your development teams or 3rd parties should the service be hosted external to your organisation. Fundamentally it is no different to any other HTTP Request in that you need:

  • URL of the service,
  • Payload,
  • Request Header (including any authorisation).

OctoPerf's new UI - Design changes

This article is the second in a series of overviews of our new UI. You can find the first one here.

This time we will dive into the changes we've made in the design phase. We've addressed many pain points from the old UI that we want to detail here:

This will make the design in OctoPerf even faster, so that you can focus more time on your tests and analyzing them.

Create virtual user

The first item on the list is obviously the new virtual user creation process. A lot of people were confused by the older UI and used the menus to get back to the project level when what they really wanted was to get back to the last step. Of course the fact that you are now required to click on Back / Next to move to the another step of the process requires one more interaction but it's also a lot easier to understand what's going on since it results from your actions. We think it's the right way to go since the only drawback is adding a couple of clicks on a process that is only used a few times per project.

To make things easier for beginners, the contextual documentation will display as soon as you select any option. It's also a better use of horizontal space that would otherwise be lost:


JMeter: test as code solutions

The rise of the CI/CD methodologies and frameworks have shaped the daily work of application developers and testers. It allowed for the creation of the DevOps model. DevOps culture demanding "everything as code", modern infrastructure tooling has grown to drive the management and configuration of infrastructure components "as code" alike.

From a load testing point of view, we already detailed how to Shift left with JMeter in this blog: Moving the JMeter testing to an earlier stage in the project lifecycle can be done by running load tests saved in a GIT repository from Jenkins. At OctoPerf we think that JMeter is one of the best tools to implement an Agile and Push to Production strategy. We explained how this approach can be useful how in a Load Test Driven Development process.

To sum up, JMeter load testing can efficiently be executed on automation servers but:

  • The JMX format is not VCS friendly, making it hard to work on as a team,
  • Using an external graphical application might be a barrier for programmers.

Application developers know that code and associated configuration files can easily be shared, versioned and reused. It's about time we **take "testing as code" seriously and bridge the gaps between development and load testing activities and teams.

The aim of this blog post is to do an overview of available solutions to do "Jmeter as code" using an existing JMX File.

OctoPerf's new UI - Overview changes

Our new UI has been available for everyone since a few weeks now. It is a major project for us that has taken several years to get to this stage. It's been a lot of effort but we're confident that it will be worth it when you see all the new possibilities.

That being said, we thought it would be helpful to ease you into it by going through some of the key features together. The goal is to talk about the major UI changes that impact most if not all the new screens. Then we'll cover the specifics of each individual steps (like design or runtime) in later blog posts.

Of course the first thing that comes to mind is the navigation through OctoPerf. And we've made a lot of changes in this area.

Left-handed menu

Left hand menu

The top menu has become a left-handed menu now. We've always been trying to keep up with properly adding the new features in the menus like we did last year. But we thought it could be improved further. Typically, we noticed that new users struggled to notice what's inside the workspace menu so we decided to split it into another "Tools" submenu.

Workspace and projects remain visible at all times in order to navigate back to their level easily. It can also be collapsed in order to save horizontal space once you are familiar with the layout and icons.

Adeo - Case study

Adeo is the European leader in the home improvement and DIY market, and number 3 worldwide. Its companies : Leroy Merlin, Bricoman, Weldom, Zôdio… Gather 150 000 leaders and more than 1000 sales points over 20 countries.

Teams all over the world enable ADEO companies be useful to inhabitants while making home a positive place to live.

Thomas Pitteman
Thomas Pitteman Very fond of everything related to computers, he worked in the transport industry before merging work with passion by joining Adeo in 2018. He is now head of load testing, responsible for harmonizing testing methodologies and the onboarding process. He was also an important part of the benchmarking process which resulted in the selection of Octoperf as the new load testing tool.

Marc Lavieville
Marc Lavieville is lead Quality Manager at Adeo. Always attracted to innovations and new challenges, he worked in many different fields before ending up creating the team responsible for quality management at Leroy Merlin. Since that project was a success, and with the emergence of platform mode operation, he was asked to contribute that team to the whole Adeo group.

While load testing was gaining traction in the company, limitations from the usual tool, were found and prevented an easy growth:

  • 5 parallel runs limitation, that could only be upgraded through a very expensive license modification,
  • Floating licensing policy which only allowed 5000 concurrent Vus for the entire company,
  • Load tests duration capped at 8 hours,
  • Insufficient resources on the load generators (2CPU / 8Gb Ram),
  • The lack of a strong relationship with the tool's support team.

All those limitations pushed ADEO to begin the process of acquiring a new tool.