DEFECT in TC 9.30 - WaitProperty Waits untill the timeout even if the property has achieved desired value

Question

- Add a WaitProperty Action for Exists Property and provide a timeout of lets say 60 Seconds

- Run the test so that it starts on some other operation and the next statement is our WaitProperty Action.

You will note that, even if our object already exists in the Object Browser, TC will still wait fr 60 seconds.

Very Annoying, I dont want to change all my 10000 tests for this single defect.

Pravin

nicktulett · Answer

There are other, better Wait commands to check for an object's existence.I can't see how WaitProperty("Exists", true, 60) could make sense or ever work.

pravin_k99 · Answer

Hello Smartbear Team,Are you looking at fixing this defect any soon?Pravin

maximojo · Answer

Can you post your script? I'm curious as to what it looks like.Why are you waiting for the "Exists" property?

maximojo · Answer

Normally you would just have:Aliases.IEXPLORE.myAlias.Existsand wait the default timeout out.you can even change the default timeout at runtime if you want it to be faster/slower for a particular comparison:Options.Run.Timeout = 500and then reset it back to the default afterward.or elseAliases.IEXPLORE.WaitAliasChild("myAlias", 1000);

hlalumiere · Answer

The oddball example should probably not be swept aside, as this was a known issue in a few earlier releases. It's not improbable that the previous fix might have been inadvertantly reverted, or did not fix the entire problem originally.

Forum Discussion

DEFECT in TC 9.30 - WaitProperty Waits untill the timeout even if the property has achieved desired value

Recent Discussions

TestExexute sometimes not recognizing object

Keys method sometimes adds period(.) in the middle of text

How to fully automate test complete UI test cases flow

Related Content

At What Frequency Does WaitProperty Checks For Property

wItemCount and WaitProperty

WaitProperty not detecting that property is not at expected value