For bug reports and questions, please use the in-app chat or email@example.com.
As a test author, I want the ability to nest flows in other flows, so that I have finer granularity of abstraction and better flow reuse.
Thought I'd try again. :)As a MABL user I would love to have this feature. For instance:As a user of my application I may want to:Flow #1: LoginFlow #2: Select my productsFlow #3: Go to shopping cardFlow #4: Enter user's info (address, city, state, etc...)Flow #5: Enter Credit Card InfoFlow #6: Submit PurchaseFlow #7: LogoutNow rather than dragging and dropping 7 flows I'd love to have 1 Master Purchase flow that does ALL 7 of those things. I'd love to give a manual tester who is wanting to run an edge case that just needs to pass parameters in, rather then help them drag the proper flows in...There are several other illustrations I can think of, but...looking forward to hearing more on this.
Any updates on this? We'll be celebrating two years of the submission of this idea shortly. :)
Here's a closely related alternative we might be able to upvote, that's sort of like nested flows, but might make it a little easier for mabl to implement. Please check it out and upvote if you like the idea! Thanks. - Jonathan. https://feedback.mabl.com/ideas/ML-I-834
This is a really big deal for us. Almost all the screens in the application have nesting. Our main one has 7 selections in column one, 94 selections in column two (combined) and 390 selections in column three (combined). If this is not possible, give us a solution that will allow this. Thank you!
Yes, this is much required feature.
This would be an immense help, specifically for the ability to create a flow that contains a loop in combination with other, non-looped steps.
I'm all for this one! I've wanted to leverage loops to find exact page elements but haven't been able to because I can't can't currently nest loop flows in my pre-existing step flows.
This would be a huge help to all of the work we're trying to do.
Yes this would be of great help!
Nesting flows within flows would be a very useful feature. We currently do something similar in our Cucumber tests by having one step which calls a number of other steps that we've built for other scenarios. There are a lot of actions which it makes sense to define in their own specific "flows", but which would commonly be grouped together.
I am running into this issue now. I need to have flows within flows. Instead now I have to run more tests cases to reach all flows individually. Allowing Nesting would be a great improvement.
Yes, that would help!
This would be a big help for us. It would simplify a lot of our journey's.
You won't be notified about changes to this idea.