Flow Controls
Last updated
Last updated
Flows provides additional features and functions that can be found in the top right corner of the editor.
Working on a flow often requires checking or verifying certain things during execution. For example, if the flow involves adding then removing an item from an online shopping cart, we might want to verify that the item was indeed added to the cart during the execution.
Exports the current flow you're viewing (in .yaml).
Duplicates the current flow on your Test Suite.
Coverts the current flow into a Load Test. See here how to setup Load testing with Loadmill.
Replaces the given parameter generated by Loadmill or by the user to a new parameter name.
ex: Loadmill uses ${origin_1} to define the base url of the test. By applying Replace Parameters you can replace ${origin1} to ${base_url}.
This only changes the name of the parameter without affecting its value.
Extracts a given value from the Test Flow into a parameter.
ex: Say you have a unique value that you want to parameterize like a visitor id, a specific name or even a phone number. You can extract those values and parameterize them by applying the Extract Parameter tool.
All parameterized values are located in the PARAMETERS tab of the suite.
Copies the current flow to the chosen suite.
As AI suggests whats wrong with the test, and gives a possible way to solve it, why wouldn't it just solve it by itself? The 'FIX IT FOR ME' button, leads to the edit-using-AI panel prompt prefilled with the suggestion AI provided before.
Then it acts like the regular 'Edit Using AI' feature explained here.
Loadmill provides the functionality to execute tests in debug mode. When the debug toggle () is turned on (), a small checkbox will appear next to each request in the flow, allowing you to set a request as the breakpoint for debugging. Once the flow is executed, the test will be paused right before the checked request is made. The results window will already show the statuses of completed requests, with a 'pending' status indicating the upcoming request, which serves as the breakpoint.
Once a flow is executed and fails, this button will appear which, using AI, provides you with a possible reason and solution for the test, according to the tests agenda. For example:
