tree: 9a0f3b785f7a5e35d884b5e0edf5315d9d6c1cb2 [path history] [tgz]
  1. docker/
  2. java/
  3. resources/
  4. scala/
  5. README.md
src/test/README.md

About this directory structure

  ./resources/com
  ./scala

To start using the files under these directories above, consider the instructions on how to use Gerrit core's Gatling framework. These are about running non-core test scenarios such as this plugin one below:

  sbt "gatling:testOnly com.ericsson.gerrit.plugins.gcconductor.scenarios.CreateChangesTriggeringGc"

This is a scenario that can serve as an example for how to start testing this plugin, along with its executor component. Both of these components should be locally installed along with default configuration. Plugin's gc-executor component is assumed to be running alongside Gerrit.

Scenario scala source files and their companion json resource ones are stored under the usual src/test directories. That structure follows the scala package one from the scenario classes. The core framework expects such a directory structure for both the scala and resources (json data) files.

There are two environment properties that can be configured:

The minute_multiplier property defines a value that get multiplied by 60 to represent the time needed by the test before creating the last change which triggers the plugin. Its default is 1 and can be set using another value:

   -Dcom.ericsson.gerrit.plugins.gcconductor.scenarios.minute_multiplier=5

The loose_objects property represents the value of loose objects required to trigger garbage collection. Its default value is 400 and can be set using another value:

   -Dcom.ericsson.gerrit.plugins.gcconductor.scenarios.loose_objects=50