You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently whenever a job with parallelism > 1, Predator spins up multiple Predator-Runners to run the load. If a before stage is configured in the test, then this before stage will run in each predator-runner meaning that the before stage will run ${parallelism} times
Describe the solution you'd like
Run the before stage only once regardless of how many runners are spun up. Once finished successfully, pass any created variables from the before stage to the rest of the test.
If in the run of the before stage any request fails or receives a status_code != 2xx, fail the run
This feature's design is open for discussion and for contributions 😁
The text was updated successfully, but these errors were encountered:
a very interesting feature, I would say that we will need a special runner that will run only the before section and submit before params to predator, then predator will spin up all parallel runners.
We need to think about how we enable this special runner to run only the before stage because currently the before stage is implemented inside artillery and how it runs the tests. We might have to patch the artillery code for this.
Is your feature request related to a problem? Please describe.
Currently whenever a job with parallelism > 1, Predator spins up multiple Predator-Runners to run the load. If a
before
stage is configured in the test, then thisbefore
stage will run in each predator-runner meaning that thebefore
stage will run${parallelism} times
Describe the solution you'd like
Run the
before
stage only once regardless of how many runners are spun up. Once finished successfully, pass any created variables from thebefore
stage to the rest of the test.If in the run of the
before
stage any request fails or receives a status_code != 2xx, fail the runThis feature's design is open for discussion and for contributions 😁
The text was updated successfully, but these errors were encountered: