Pearson, founded in the 19th century, is one of the world leaders in providing education services all around the globe. Francisco Muniz is the Performance Architect for Pearson, responsible for Performance Alignment across Pearson’s Virtual Learning. This position entails working with many different parts of the organization, such as Architecture, Development, and QA. As such, Francisco was leading and overseeing the important Octoperf and Loadrunner software switching project.

This post does not look at a particular aspect of JMeter nor does it give a detailed overview of how to use a particular tool that will compliment your performance testing with JMeter. What it is about is the principles of push to production pipelines and performance testing and while I have stated that this post is not specifically about JMeter in my experience JMeter is one of the best performance testing tools for this type of pipeline integration.

In this post we are going to look at WebSockets, specifically how JMeter can be used to test them. Web Sockets are not supported natively by JMeter but there are a couple of Plugins that you can use that work very nicely. One of them is called JMeter WebSocket Sampler by Maciej Zaleski and information on the library can be found here. The second and the one we will use for our post is also called JMeter WebSocket Sampler and is by Peter Doornbosch, more information on this Plugin can be found here.

There are many samplers that JMeter provides but I am willing to bet that the HTTP Request samplers is the most frequently used and, in this Blog Post, we are going to look at how this works and how it can be configured.

Dynatrace is a cloud monitoring platform and is used by many organisations to measure the performance of their production systems and to set thresholds against which performance tolerance are measured. During testing Dynatrace can be used to monitor how the application under test responds during your performance tests as well as providing the capability to drill down into performance issues you may need to investigate.

You may have heard the term shift-left testing which is essentially moving the testing to an earlier stage in the project lifecycle, essentially the activity is moved to the left on the project timeline. The benefits of testing earlier have always been understood but not always happened when we consider performance testing which in some cases is still left until the very end of the delivery process.

The focus of OctoPerf 12.4 is on integrations, first in regards to creating test scripts through our new Postman import released a few weeks ago. Through postman we also open OctoPerf to swagger and open API imports. Microsoft Teams is also on the menu in terms of alerting before/after the tests, but the main dish is the backend listeners. Through these you can have our load generators send metrics to your own database in real time during the test.

Qytera software is a company dedicated to providing fast and effective quality assurance for their customers. Their area of expertise includes Test Management, Test Automation, Continuous Testing and Agile Testing. All of this centered around the latest web and mobile technologies.

In this blog post we are going to look at several JMeter Controllers, specifically: This is not an exhaustive list of controllers that JMeter offers but these once will give you a clear insight into how controllers are integral in defining load testing scenarios and how without them you will struggle to build complex and indicative load tests.

We’ve been working a lot behind the scenes for this release because we wanted to address the license sharing issue. Up until today it was only possible to ask us to share the license for you and sharing could only share every license you own. We had to completely refactor the way we handle licenses to allow you to decide on your own to share all or a fraction of your subscriptions. But that’s not all, we also worked on a VU validation with multiple iterations.