Feature Request with Variables
Posted: Fri Mar 25, 2011 1:57 pm
First off, I really like a lot of the new features with 3.0, especially the implementation of Variables. It would be really great if you could use the variables more extensively in the GUI though.
1) It would be useful to have actions only trigger when a variable is set to a certain value. We have several tests we could combine and many more we could create if variables were able to enable/disable an action within a recording.
2) The ability to set the value of a variable based on an accessibility value. We are forced to have user code to do the following, which we do quite often (NumberVariable is our variable):
Accessible accElement = new Accessible(repo.Properties.ListItemNumber);
NumberVariable = accElement.Value;
3) The ability to pass parameters to a user code method through the recording. Even just the ability to pass a list of strings separated by commas would be extremely useful, we could cast to integers, floats, etc in the user code. Currently we have methods that check a table for a specific string value, or list of values, so we have to make a lot of helper user code functions to call to pass the parameters we want from the recording.
Thank you for taking this feedback into consideration. Ranorex 3.0 is a big improvement over 2.3 and our company looks forward to the new features you guys are adding.
1) It would be useful to have actions only trigger when a variable is set to a certain value. We have several tests we could combine and many more we could create if variables were able to enable/disable an action within a recording.
2) The ability to set the value of a variable based on an accessibility value. We are forced to have user code to do the following, which we do quite often (NumberVariable is our variable):
Accessible accElement = new Accessible(repo.Properties.ListItemNumber);
NumberVariable = accElement.Value;
3) The ability to pass parameters to a user code method through the recording. Even just the ability to pass a list of strings separated by commas would be extremely useful, we could cast to integers, floats, etc in the user code. Currently we have methods that check a table for a specific string value, or list of values, so we have to make a lot of helper user code functions to call to pass the parameters we want from the recording.
Thank you for taking this feedback into consideration. Ranorex 3.0 is a big improvement over 2.3 and our company looks forward to the new features you guys are adding.