[Bug]: Unable to run gatling tests using gradlePlugin within pod

[andrzejmikolajczakds]

Pre-requisites

• I'd like to contribute the fix myself

What happened/what you expected to happen?

Created pod can not run task gatlingRun-MY_CLASS_NAME.
It is because of wrong placeholder here.
According to documentation it should be:
gradle gatlingRun --simulation MY_CLASS_NAME

Relevant log output

No response

[kane8n]

@andrzejmikolajczakds
Thank you for creating the issue!
This is similar to the following PullRequest.

• Gatling 3.11 upgrade #120

The current implementation works with gatling 3.10, but not with 3.11 as you mentioned.
The standard ---simulation CLASS_NAME option is enforced in gatling 3.11.

• Reference
  • https://docs.gatling.io/release-notes/oss/upgrading/3.10-to-3.11/#upgrading-the-gatling-gradle-plugin-to-3110

Until 3.10, it was gatlingRun-MY_CLASS_NAME.

There are plans to make gatling-operator compatible with gatling 3.11, but the timing is not yet determined.

[andrzejmikolajczakds]

So maybe we could update doc: https://github.com/st-tech/gatling-operator/blob/main/docs/user-guide.md#create-custom-gatling-image-with-gradle-gatling-plugin . There is a link to sample repo, which uses gatling 3.11

[kane8n]

@andrzejmikolajczakds
Please submit a PullRequest for document updates and we will review it!