Skip to content

Load Testing Blog

Gatling: Simulation Scripts Parameterization

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:

Gatling: Getting Started With Simulation Scripts

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.

Fullstack Reactive Server Sent Events

Reactive programming is a programming paradigm aimed at maintaining overall coherence by propagating changes from a reactive source (modification of a variable, user input, etc.) to elements dependent on this source.

Reactive applications are more and more important today as they are:

  • Highly Available: the system must respond quickly no matter what,
  • Resilient: the system must always remain available, even in case of error or even if it is overloaded,
  • Message Oriented: the system uses asynchronous messages.

Which meets the requirements of today's users.

Test camp 2019: OctoPerf in Poland

For our first time in Poland, we decided to attend to TestCamp conference. TestCamp is an event-based in Wroclaw, Poland. Test Army is behind the organisation. This event was split in two days, the first one, we trained a few people on OctoPerf. The second one as exhibitor and speaker. More than 500 people attended on Saturday, which is quite an impressive number.

How To Deploy InfluxDB / Telegraf / Grafana on K8s?

This article follows our first blog post related to deployment on Kubernetes. It is a step-by-step guide explaining how to deploy the InfluxDb/Telegraf/Grafana stack.

More importantly we will se:

Here again we rely on declarative configuration of K8s to install the InfluxDB/Grafana stack. It's the easiest way to do since there are many configuration objects to create.