Flow Execution
Running with Overrides
Assigning Labels
Flow Labeling is an efficient way to save time and enhance productivity during application testing. By executing only relevant flows, you can avoid redundant testing and concentrate on critical aspects.
To utilize Flow Labeling, simply label your flows with specific keywords for identification. Then, assign these labels to relevant sections of your application's CI. This ensures that only relevant flows are executed when changes are made.
Testing and validation are crucial in product and software development, but maintaining this process amidst diverse requirements can be challenging. Flow labeling is essential for developers to effectively test every aspect of their product.
You may need to test multiple operations or ensure your application loads correctly. However, each update or bug fix undergoes a categorical test scenario that may not encompass all test cases from your Test Suite/Plan.
The following Test Suite represents a user management application with 6 different flows. Each flow is labeled "operation" or "sanity" or both.
Make sure your flow is attached to the CI in order to run it based on labels.
Installing Loadmill NPM Package
Before you start, install the Loadmill NPM Package.
Running Labeled Flows via CLI
Now that we've labeled our flows correctly, we'll run them according to label we pass in to the command line. We want to run all flows within a test suite that are labeled "sanity".
Let's quickly tour what values you need before running our tests.
Open your CLI and run the following command:
To conclude, flow labels allow us to focus our tests based on our needs regardless of the amount of test cases we have on our test suites or test plans. We could schedule daily test runs on "sanity" labeled flows and run "operation" flows for every time we push an update to our code.
Last updated