# Run all simulation scripts with maven command

**URL:** <https://community.gatling.io/t/run-all-simulation-scripts-with-maven-command/9008>\
**Category:** Gatling (Open-Source)\
**Created:** [May 21, 2024, 9:22am UTC](https://community.gatling.io/t/run-all-simulation-scripts-with-maven-command/9008 "2024-05-21T09:22:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Slaym](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@Slaym](https://community.gatling.io/u/Slaym)\
**Post date:** [May 21, 2024, 9:22am UTC](https://community.gatling.io/t/run-all-simulation-scripts-with-maven-command/9008/1 "2024-05-21T09:22:42Z")

</div>

**Gatling version** : 3.11.2 (must be up to date)  
**Gatling flavor** : java  
**Gatling build tool** : maven

Hello,  
I want run all simulation classes in my project with one maven command, the main goal is to include this maven command in the CI/CD pipeline.

I’m using gatling-maven-plugin, but when i read the documentation I understand that it’s not possible to run all script with this plugin :

```auto
The `gatling:test` goal runs in interactive mode and suggests the simulation class to launch unless:
* there’s only one simulation available,
* or the Simulation class is forced with the `-Dgatling.simulationClass=<FullyQualifiedClassName>` Java System Property,
* or the non-interactive mode is forced, in which case the task will fail if there is more than 1 simulation available,
* or it’s in batch mode (`-B` Maven option), in which case the task will fail if there is more than 1 simulation available,
* or the `CI` env var is set to `true`, in which case the task will fail if there is more than 1 simulation available.

```

The `execute` goal it’s not exist to run all simulation script.  
I use `gatling-maven-plugin` version `4.9.0`

My questions :

1. how I can run all simulation scripts with a single maven command ?
2. If this is not possible, how can I group all the scripts to run them from a single maven command or from a java main class (note that the Gatling-build-property class no longer exists)

Thnaks in advance 🙂

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [May 21, 2024, 9:47am UTC](https://community.gatling.io/t/run-all-simulation-scripts-with-maven-command/9008/2 "2024-05-21T09:47:24Z")

</div>

From the [documentation](https://docs.gatling.io/reference/extensions/build-tools/maven-plugin/#running-your-simulations):

> Use `mvn gatling:help -Ddetail=true -Dgoal=test` to print the description of all the available configuration options on the `test` goal.

Then, IMO, this usage doesn’t make much sense:

- in which order would the different load tests be triggered?
- what is the expected behavior when one test has failing assertions?
- how do the application state modifications by a previous simulation impact following ones?

Load tests are not unit tests. They should run in isolation.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/b/b148e0742de35c6280726cabf3ecd3de2d320f63.png) [@system](https://community.gatling.io/u/system)\
**Post date:** [June 20, 2024, 9:48am UTC](https://community.gatling.io/t/run-all-simulation-scripts-with-maven-command/9008/3 "2024-06-20T09:48:07Z")

</div>

Closed on June 20, 2024, 9:48am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.