To implement missing or alternative functionality, GeekLoad provides the ability to work together with various third-party tools.
For all cases of integration, it works within the rules of the relevant software regarding the installation of plugins, etc.
The most important topics to get started with plugins are Project and Reporting. Read them first.
To debug GeekLoad projects and manually investigate performance issues, you can use a plugin for VS Code.
This plugin allows you to edit *.gl-js files with GeekLoad scripts using syntax highlighting and intellisense.
A Gradle plugin is designed to solve the problem of automatically checking services during the build process.
GeekLoad uses all compatible projects (*.gl-js) in the src/test subfolder of your project as tests.
First of all, you need to prepare one or more GeekLoad projects and save them in src/test subfolder of your project.
Next, to prepare your gradle project, add this dependency to build.gradle:
After loading, the plugin will add the geek-load task to the test group. Use this task separately or as a dependency for the target task of a complete project build to test your application or service.
A TestKube executor provides yet another way of load testing in the TestKube infrastructure.
To create tests based on GeekLoad, you need to create a custom executor using the following values:
After creating the executor, you can add any number of load tests by specifying the following parameters: