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
#457 implements setup & teardown lifecycle hooks for tests. However, it doesn't implement the necessary hooks for the feature to work with cloud/distributed execution, namely:
We need to be able to run only the setup function (and pause) and then distribute the result/return of the setup function to all nodes' export default function:
We need to be able to extract the data returned by the setup() call from the node where it was run, and pass it to all other nodes' export default function. Maybe through the REST API? So, you could start k6 with something like:
run k6 cloud --run-setup-then-pause script.js
extract the setupData
pass it to all nodes (k6 run --setup-data "..." or via REST API), and then unpause all nodes to begin execution
The intent is to merge #457 first to make it available in k6 for local execution and then implement what's outlined in this issue to gain the necessary cloud/distributed execution support.
The text was updated successfully, but these errors were encountered:
#457 implements setup & teardown lifecycle hooks for tests. However, it doesn't implement the necessary hooks for the feature to work with cloud/distributed execution, namely:
We need to be able to run only the setup function (and pause) and then distribute the result/return of the setup function to all nodes'
export default function
:We need to be able to extract the data returned by the
setup()
call from the node where it was run, and pass it to all other nodes'export default function
. Maybe through the REST API? So, you could start k6 with something like:k6 cloud --run-setup-then-pause script.js
setupData
The intent is to merge #457 first to make it available in k6 for local execution and then implement what's outlined in this issue to gain the necessary cloud/distributed execution support.
The text was updated successfully, but these errors were encountered: