Create an analogue of the Browser/Data-driven Loop operations that can be applied to the Test Items
As the Test Items tree is the primary means for tests organizing, it will be pretty handy if you guys implement an analogue of the Browser Loop and Data Driven Loop operations that can be put at any location within Test Items tree (i.e. as a root item or as some sub-node) and handle execution if its child items.
To make things even more perfect, those analogues should be parameterized (via e.g. Project Variables) - i.e. it should be possible to dynamically specify what, say, browsers must be included in the Browser Loop analogue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.