Hassy Veldstra

Oh and `DD_APP_KEY` is indeed not a requirement (it used to be)

I'm hesitant to introduce another way to load custom JS code; we should be able to reuse the existing `config.processor` option to provide additional functions for template strings. Another thought...

hi @MickL 👋 Cookies (and any other VU-specific data) aren't propagated from a `before` section into VU scenarios. Only variables created with `capture` will be available to VUs. This is...

Expectations are on the roadmap.

This could be done with a custom `afterResponse` JS function rather than by extending the internal stats object. Any reason that wouldn't work for your use-case?

hi folks 👋 got a fix for you! 1. We just updated the docs to mention that using `ensure` in Artillery v2 needs `artillery-plugin-ensure` to be installed. Sorry about that,...

@jclusso oops, a case of documentation being updated **before** a new release and going out of sync 🤦‍♂️ Could you try again with the latest version of `artillery` and `artillery-plugin-ensure`...

That's interesting @mac-chaffee. The original use case was indeed to embed reports into Jenkins, but today most of our users upload reports to S3/another hosting service, and share those URLs...

The functionality you want sounds similar to this: https://www.artillery.io/docs/guides/guides/test-script-reference#ensure---slo-checks But instead of evaluating at the end of the test run, you'd like for it to be evaluated continuously during the...

I don't think there's a way to do it right now @toxtox7, but it would be a good feature to add.