Hassy Veldstra

There's an easier way to work with a local plugin whilst developing it. The README for the example plugin @juanig1 linked mentions it, but I'll add it to the main...

For anyone looking for a way to run Playwright tests as load tests today: https://github.com/artilleryio/artillery-engine-playwright This lets you define load phases, ramps, and tracks and reports failure rates for scenarios,...

Artillery reports requests served per second in its output.

There's no way to `capture` the response code at the moment. You have two options that may help: 1. Run `artillery` with `DEBUG=http,http:response` to print the details of every HTTP...

There's no way to associate a scenario definition with a specific phase right now, but you may be able to do it with custom logic in a `beforeScenario` function or...

@brianjenkins94 file uploads are known to work well. There's a DIY solution here: https://github.com/shoreditch-ops/artillery/issues/320#issuecomment-329448748. If you need a solution which just works out of the box, and also works when...

Which version of Artillery are you running?

It's one of those features that looks like a bug. Custom stats are not included in the final aggregate report because there's not information to be able to compute aggregate...

File uploads are not implemented yet, the `@file` syntax does not work.

Two options here: 1. Someone submits a PR which makes it work 2. Your team buys a license for [Artillery Pro](https://artillery.io/pro/) which supports file uploads (along with lots of other...