Comment on page
Flow Labeling is a great way to save time and improve efficiency when testing your application. By only running relevant flows, you can avoid redundant testing and focus on what's important.
In order to use Flow Labeling, you simply need to label your flows with specific keywords that identify them. You can then assign these labels to certain parts of your application's CI. When a change is made, only the relevant flows will be run.
Testing and validation is a critical process in product and software development, but it can be tough to maintain this process with so much variety. Labeling flows is an essential part of the testing and validation process that helps developers test every aspect of their pending product.
You may want to test multiple operations or test that your application loads correctly. Even so, every updated code to improve your application or fix a specific bug in your application passes through a categorial test scenario that doesn't include all the test cases created in your Test Suite/Plan.
Creating and assigning labels to flows is a quick and easy process with Loadmill. Simply select the flow and click on the label icon
to assign a label of your choice.
You can assign pre-made label or create a new one yourself.
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.
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:
loadmill <test-suite-id> --test-suite -w -t <token> --labels --report "label1,label2"
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.