Krkn and krkn-hub links lead to 404 error pages
Currently:
“Scaffolds a basic execution plan structure in json format for all the scenario names provided. The default structure is a serial execution with a root node and each node depends on the other starting from the root. Starting from this configuration it is possible to define complex scenarios changing the dependencies between the nodes. Will be provided a random id for each scenario and the dependency will be defined through the depends_on attribute. The scenario id is not strictly dependent on the scenario type so it’s perfectly legit to repeat the same scenario type (with the same or different attributes) varying the scenario Id and the dependencies accordingly.”
Instead:
Scaffolds generates a basic execution plan structure in json format for all the scenario names provided. The default structure is a serial execution with a root node, and each node depends on the other starting from the root. From this configuration, it is possible to define complex scenarios changing the dependencies between the nodes. Each scenario will be provided a random id and the dependency will be defined through the depends_on attribute. The scenario id is not strictly dependent on the scenario type so it’s perfectly legitimate to repeat the same scenario type (with the same or different attributes) varying the scenario id and the dependencies accordingly.
Currently:
if set this flag will add global environment variables to each scenario in the graph”
Instead:
If set, this flag will add global environment variables to each scenario in the graph.
scaffold [flags]
Scale testing link was not opening
Krkn and krkn-hub links lead to 404 error pages
Currently:
“Scaffolds a basic execution plan structure in json format for all the scenario names provided. The default structure is a serial execution with a root node and each node depends on the other starting from the root. Starting from this configuration it is possible to define complex scenarios changing the dependencies between the nodes. Will be provided a random id for each scenario and the dependency will be defined through the depends_on attribute. The scenario id is not strictly dependent on the scenario type so it’s perfectly legit to repeat the same scenario type (with the same or different attributes) varying the scenario Id and the dependencies accordingly.”
Instead:
Scaffolds generates a basic execution plan structure in json format for all the scenario names provided. The default structure is a serial execution with a root node, and each node depends on the other starting from the root. From this configuration, it is possible to define complex scenarios changing the dependencies between the nodes. Each scenario will be provided a random id and the dependency will be defined through the depends_on attribute. The scenario id is not strictly dependent on the scenario type so it’s perfectly legitimate to repeat the same scenario type (with the same or different attributes) varying the scenario id and the dependencies accordingly.
Currently:
if set this flag will add global environment variables to each scenario in the graph”
Instead:
If set, this flag will add global environment variables to each scenario in the graph.
scaffold [flags]
Scale testing link was not opening