.NET uses scope to indicate the appropriate values and methods that are available at given levels of software.
Ranorex Studio is not following the principle of lowest scope when attempting to auto-bind variables to data.
Ranorex is binding global parameters before local, which is reversed from what .NET does. Variables should always attempt to bind to the lowest scoped data available, so if there is a local data source that contains the same column name as a global parameter, the data source's column should win.
If the test creator wants to re-bind to a higher level data source, that should require manual manipulation.
For example, if the test is setup like the following:
Code: Select all
TestSuite --> Global Parameters (Value1=12) TestCase1 --> Test Case Parameters (Value1=34), DataConnector(Value1=56) Recording1 --> Variables (Value1)
I could have sworn that this worked correctly in earlier versions, but I haven't gone back to test it.