Wait For Control in Coded UI Testing

Wait is one of the most important operation in any automation testing tool, since we must/may need to wait for a control to fully appear in screen before performing further operations. Thread.Sleep can be used as opposed to Wait, but it’s always a bad practice to use it in code, since this will make our code to wait for time specified explicitly, even if the control appears or enabled on the screen, thread.sleep will make your code to wait for the time. Coded UI on the other hand offers different types of wait methods which is shipped along with Visual Studio as shown below

Here is the complete video explanation of different wait methods in coded UI testing. Here is the complete code from the above video

public void WaitForControl(PropertyType type, string propertyvalue) where T : HtmlControl
{

    HtmlControl genericControl = (T)Activator.CreateInstance(typeof(T), new object[] { ParentWindow });
    if (type == PropertyType.Name)
        genericControl.SearchProperties[HtmlControl.PropertyNames.Name] = propertyvalue;
    else if (type == PropertyType.Id)
        genericControl.SearchProperties[HtmlControl.PropertyNames.Id] = propertyvalue;

    //Wait For the control
    genericControl.WaitForControlCondition(x => genericControl.WaitForControlPropertyEqual(type.ToString(), propertyvalue));

}

Thanks for watching the video and reading the article !!! Please leave your comments and let me know if there is anything needed to be improved in the post !!! Thanks, Karthik KK