Improve databinding UI
The current way of how databinding and data connectors work is great. What is a little bit unhandy is how user sets and changes the binding. Currently you open a parameter and set to which module variable it will be bound (see binding_direction.png). What would be better is the ability to open the binding dialog for given module and set what paramater will be bound to what module variable (see dialog.png).
It wouldn't change anything inside the binding mechanism. The only thing needed is the enhanced UI. In fact, all the information are stored in the *.rxtst file and if it was possible I would code the enhanced UI myself (I could probably still do it but it would be outside Ranorex, that's not handy ...).
The need for this feature comes when you work with complex test cases when you have several (often the same) modules in one TC and you want to bind different values to each instance. Or if you just want to change one value (from one parameter to another) and you simply cannot find to what exact module instance it is bound.
Thank you for this input.
With Ranorex 9.2 (which will be released next week) we have overhauled the data binding experience and we also introduce a new data binding pad that gives a better overview.
Thomas from the Ranorex Product Management Team
This is a very good and appreciated idea. In case you're starting to rework data binding within the next two versions please consider the following. A good enhancement would be the possibility to globally bind variables at once instead of several instances.
For example: You have a repository used in 10 recording modules and introduce a new repository variable "variable1". In this case you would have to open 10 data bindings in order to bind this value although you use this just in 2 effectively.
If you require some further input on this idea just let me know.
Marcel Zerdin commented
In my opinion the whole data binding, local, global parameters etc. needs to be made more clear because if you have as the OP mentions a lot of modules or modules with the same name you can quickly lose the overview over your data bindings. And then it is a pain in the a** to find the wrong binding sometimes if you made a mistake there.
"...The need for this feature comes when you work with complex test cases when you have several (often the same) modules in one TC and you want to bind different values to each instance...."
Douglas Vaughan commented
I agree wholeheartedly with this feature request. The ability to review the data binding context from listing bound module variables by parameter to listing parameter bindings by module variable would be extremely helpful.
I would go further though and ask for additional information like whether the parameter is using the setter or getter in a particular situation. This would help track where a particular value is coming from and then used.