Skip to content

Load-Testing

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.

A Guide to Non-Functional Requirements

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 world of non-functional testing can be murky and ambiguous in contrast to its functional counterpart where expected functionality and behaviour is easier to define.

Hopefully this blog post will give some insight in to how non-functional requirements can be tackled and made testable.

JMeter vs SoapUI

There are many functional and load testing tools available on the market. That's great!

The most renewed open-source tools are certainly JMeter and SoapUI.

But, I'm sure you agree to say that it's difficult to know which one best suits your needs:

  • What features has JMeter?
  • What are the pros of using SoapUI?
  • Which tool has best community? User experience? Script maintainability?
  • Should I use JMeter or SoapUI? Or maybe both?

Gain significant insight on JMeter and SoapUI differences by reading this blog post that compares them on many different fields:

Ready for some action? Let's go!

Performance, Load and Stress Testing Explained

This is a typical questions QA Engineers and Devops may be asked during an interview. And we know how confusing these tests can be.

That's why we've written this article to explain once and for all the key differences between all types of performance testing.

As stated on Software Performance Testing, there are many different ways to test software including:

Each type of testing has its own set of rules and goals. Let's explore which type of testing you should use, when and the results you get.

Let's start our visual tour!

Soap vs Rest (Why comparing them is a nonsense)

I know you won't like this answer... But SOAP vs REST is not the right question to ask. Rest, unlike Soap, is an architectural style, not a protocol. To better understand REST, one should read RESTful Design Principles.

Okay, but Why do some people like SOAP while others love REST? Why is there such a strong emotion around those two names?

Because the best way to compare things is to compare them point by point, we have created a huge table which compares Soap to Rest with 10+ different criterias.