> yes, i just forgot the () ..
Parenthesis are required for JavaScript only and until now JavaScript was not mentioned in any way... 😉
To wait for a property you can use .. WaitProperty 😁
To measure time, several methods exists, choose one.
aqPerformance is a good one.
So you can use this :
aqPerformance.Start("DefaultCounter", false);
if (!yourButtonObject.WaitProperty("Enabled", true, 30000))
throw Error("TC Failed : Enabled button state not occured within 30s !");
Log.Message("TC Success : Enabled button state occured in " + aqPerformance.Value + "ms");
Hello BenoitB , I must be doing something wrong, can you check my code?
I placed your example in my script, which will be called by the main keyword, the script will be called when the option to show the button is clicked, once is clicked the following function is run, but it keeps choosing "throw error", I am sure it has not been 30 seconds, in other words, it fails right away.
function WaitForButton()
{
var button = Aliases.browser.pageExam.buttonOn
aqPerformance.Start("DefaultCounter", false);
if (button.WaitProperty("Enabled", true, 30000))
throw Error("TC Failed : Enabled button state not occured within 30s !");
Log.Message("TC Success : Enabled button state occured in " + aqPerformance.Value + "ms");
}
Does your button has the Enabled property ?
The WaitProperty exit directly (what you have) when the property asked is missing :
If the property achieves the specified value within the timeout, the method returns True. Otherwise, if the timeout elapses before the property achieves the specified value, the method returns False.
Also, False if the object does not have the specified property.
Put a breakpoint on line aqPerformance.Start("DefaultCounter", false); and when you come in, spy the button object.
Hi,
> var button = Aliases.browser.pageExam.buttonOn
Is it guaranteed that buttonOn exists at the moment when this line of code is executed?
If it is not guaranteed then try to replace the above line with
var button = Aliases.browser.pageExam.WaitAliasChild("buttonOn", 30000);
Does this help?
Hello
Yes, the button is displayed on the screen. To test I manually called up the dialog with the button disabled,
I then execute the script and wait for the button to become enabled but the script fails right away (takes the throw error path). Tried WaitAliasChild and I get the same failure.
I added the script to the keyword test, when the option to open the dialog is called, the script is run so both (manually/automatically)
Can you review the Object spy copied within this trail of messages, I also added how the button looks?
Hi,
nedbacan wrote:
it keeps choosing "throw error", I am sure it has not been 30 seconds, in other words, it fails right away.
function WaitForButton()
{var button = Aliases.browser.pageExam.buttonOn
aqPerformance.Start("DefaultCounter", false);
if (button.WaitProperty("Enabled", true, 30000))
throw Error("TC Failed : Enabled button state not occured within 30s !");
Log.Message("TC Success : Enabled button state occured in " + aqPerformance.Value + "ms");
}
If you are talking about this code, then it works as expected:
-- The button becomes enabled within 30 seconds;
-- WaitProperty() returns 'true';
-- line with 'throw' statement is executed.
Code by Benoit was like this:
if (!button.WaitProperty("Enabled", true, 30000))
(note exclamation sign before 'button').
Does this help?