Rolling back to 11.20 has resolved the issue. Support is looking into the problem with 11.31.
There are events which are triggered but the code hasn't changed since upgrading from 11.20. The error only happens in TC 11.31.
It could very well be that TC 11.31 is running more efficiently and so is actually executing the tests a bit faster, perhaps catching the objects before they are recreated.
Since there are events that fire upon certain changes, I would suggest a best practice would be to use WaitNNN methods for different interactive steps in order to ensure that the object is ready for input before you attempt to use it.
tristaanogre wrote:It could very well be that TC 11.31 is running more efficiently and so is actually executing the tests a bit faster, perhaps catching the objects before they are recreated.
Since there are events that fire upon certain changes, I would suggest a best practice would be to use WaitNNN methods for different interactive steps in order to ensure that the object is ready for input before you attempt to use it.
It does seem 11.31 executes quicker and catching the textbox while re-loaded. I have tried WaitAliasChild without success and not willing to put any sort of random delay between the SetText and Keys.
Where are you putting WaitAliasChild? It may be that you will need more than one call, depending upon where your application events are firing.
tristaanogre wrote:Where are you putting WaitAliasChild? It may be that you will need more than one call, depending upon where your application events are firing.
Between the SetText and Keys
