BUG: Ranorex displays incorrect value during debugging
Posted: Thu Jan 23, 2014 11:26 pm
I thought I posted about this once, but maybe I've not. I've attached the only convenient example I have, though I can find more if it's really necessary.
This has cost more than one of us hours of wasted time because Ranorex is showing the INCORRECT value in the debugger during runtime. We wasted so much time trying to figure out what we did wrong, finally we wrote the value to the report and saw that it was what we expected, just the debugger was wrong.
In the attached example, if I delve further into the private values of the properties, I can find the correct value. However, depending on the complexity of the object, its properties and perhaps some other variables that I can't think of right now, you cannot find the right value you must output it to the report.
That's really unacceptable. If I do the same process in VS, it will evaluate the properties correctly.
This has cost more than one of us hours of wasted time because Ranorex is showing the INCORRECT value in the debugger during runtime. We wasted so much time trying to figure out what we did wrong, finally we wrote the value to the report and saw that it was what we expected, just the debugger was wrong.
In the attached example, if I delve further into the private values of the properties, I can find the correct value. However, depending on the complexity of the object, its properties and perhaps some other variables that I can't think of right now, you cannot find the right value you must output it to the report.
That's really unacceptable. If I do the same process in VS, it will evaluate the properties correctly.