Hassy Veldstra

The reason is zero-config discovery of plugins, i.e. as a user you just need to add the name of the plugin + its settings to your test script, and Artillery...

Cool. Will gladly accept a PR which allows something like: ``` yaml config: plugins: some-custom-plugin: package: "@prefix/some-package-name" option1: "something" option2: "somethingElse" scenarios: # ... ``` To load the plugin from...

You need to fork and send a pull request. On Friday, 28 October 2016, Treasure Mathala [email protected] wrote: > I don't seem to have write access to this repo, I...

Two things to do before we can close this: 1. make the trailing slash in the `scope` attribute optional 2. document the change

Nice. Would it make sense to support a `timeout` option, which would abort the scenario with an error if the responses aren't received within a certain time window?

Hey @JohnieLee, no that's not supported by the templating engine at the moment.

@steveschnepp could you give an example? Do you mean being able to loop through an array that comes back in a JSON response?

@steveschnepp Great, just wanted to make sure I understood the use-case.

@kapekost Artillery's templates don't really support arrays - so that would require some significant changes which aren't planned for a particular release right now. It is possible to create a...

[YAML references](https://gist.github.com/bowsersenior/979804) can be used for this. For example, something like: ```yaml # # this can be anywhere in the YAML file that defines the test: # subflow-add-book-to-cart: &subflow-add-book-to-cart -...