Skip to content

What is Kraken's Gatling Application Purpose?

Usage

The Gatling application is used to ease load and performance tests made with Gatling:

  • Easily import HAR files or Gatling .scala test scripts,
  • Compare test executions with records (or compare successive test executions),
  • Visualize results during the load test execution thanks to Grafana.

Gatling App

Features List

The Gatling and Administration frontends share the same DNA.

But the Gatling Application offers an improved user experience to conduct load tests, with:

Info

All actions related to load tests (importing HAR files, debugging or running simulations) are in fact shell script file executions with the proper environment variables. You can customize these script in the advanced configuration.

So, anything that can be done in the Administration view, can also be done in the Gatling view, except:

Note

Open the Administration App in a new browser tab to access configuration files and view Docker container logs if needed.

Simulations Tree

The simulations tree is located at the upper-left corner of the application. It displays all folders and files for the root directory $GATLING_HOME/user-files/simulations/.

Gatling Simulations Tree

In addition to all basic file tree features, this one allows you to:

Resources Tree

The resources tree is located at the lower-left corner of the application. It displays all folders and files for the root directory $GATLING_HOME/user-files/resources/

Gatling Resources Tree

It offers no additional features than the ability to import external files used in your Gatling simulations.

Gatling Test Results

The test results table is located at the upper-right corner of the application.

Gatling Test Results

A new row is added to the table each time you import an HAR, debug a test or run a simulation:

Column Description Tip
Status The result status, displayed as an icon, from STARTING, RUNNING, COMPLETED, CANCELED or FAILED. Place your cursor over the icon to display the status as a text value.
Run Description The result description, entered while starting the test. The preceding icon displays the type of result: HAR, DEBUG or RUN.
Date The test start date. Place your cursor over the date to display both the start and end date of the test.

The rightmost column displays a Menu Icon icon that opens a menu.

Gatling Test Results Menu

This menu allows you to:

Click on a row to select it. Selecting a Debug result or an HAR import automatically opens the debug table, displaying the associated debug entries.

Info

Deleting a test result induces the following actions:

  • Removal of the Galting HTML report if any,
  • Removal of the Grafana dashboard and associated InfluxDB data (if any),
  • Removal of associated test results files (includes the debug entries!)

Tip

Click on a column header to sort the results table.

Debug Table

The debug table is located at the lower-right corner of the application.

Debug Table

A new row is added to the table for each debug request/response for the currently selected Debug result:

Column Description Tip
Status The debug status, displayed as an icon. OR or KO. Place your cursor over the icon to display the detailed status as a text value.
Name The request name Place your cursor over the name to display the request method and URL.
Date The request time.

The rightmost column displays a Menu Icon icon that opens a menu.

Compare Debug Menu Item

This menu allows you to compare two debug entries.

Click on a row to select it. Selecting a Debug entry opens the debug editor, displaying detailed information for the request/response couple.

Tip

Click on a column header to sort the debug table.

Gatling Executions

The Gatling Executions panel is visible at the bottom-left of the application. It is un every way similar to the Command Executions panel

Only its name changes.