Open yorugac opened 10 months ago
If we find a way of defining a good API then probably we don't need to limit this to setup
. For sure, it is required for the first iteration, but after https://github.com/grafana/k6/issues/1321 has been implemented then we might be able to set thresholds more dynamically.
Feature Description
Currently thresholds can be defined only in init context, as part of
options
const object. This has its limitations: if threshold must depend on a value unavailable in init context, it cannot be defined.Such a value could be:
In many cases, one can try to add workarounds: e.g. passing some additional env vars from the outside, etc. But it would be better and have greater readability to have definition of threshold happen in
setup
instead with something like:Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
Somewhat related: https://github.com/grafana/k6/issues/785