Skip to content
This repository was archived by the owner on Oct 24, 2025. It is now read-only.

Latest commit

 

History

History
36 lines (23 loc) · 1.37 KB

customization.md

File metadata and controls

36 lines (23 loc) · 1.37 KB

Stroppy project run customization

This document provides a guide to customizing the behavior of the Stroppy project.

Overview

Stroppy use config files to handle its behavior.

In this guide, we will focus on the following config files:

  • run-config.yaml(.json)
  • descriptor.yaml(.json)

Note: json-schema can be found in tools/json_schema forlder

Customization targets

k6.ts

In run-config file, you can specify many k6 configuration options, main of them are:

  • k6BinaryPath: The path to the k6 binary (required). Can be customized with building new from sources.
  • k6ScriptPath: The path to the k6 test script (required). Can be customized with writing new by yourself (read k6-docs).
  • k6Args: An array of arguments to pass to the k6 binary.

driver binary

The default driver binary path is <workdir>/postgresql. In run-config file, you can specify many driver configuration options, main of them are:

  • driverPluginPath: The path to the driver plugin binary (required). Can be customized with building new from sources.
  • url: The database connection URL.
  • dbSpecific: An object containing database-specific configuration options.

Summary

In fact, using Stroppy, you can customize almost all the behavior of a project. Even make a redis driver and random load k6 or or whatever comes to your mind.