XQuery

estComplete provides you with access to methods and properties of web page elements, so you can search all web page elements and find the desired text in the element properties. To perform the search, you can use the Page object’s Find method. This method uses three parameters: Page.NativeWebObject.Find(PropertyName, KeyValue, TagName)

► PropertyName - Name of the property, whose value is checked by the method. Typically, the element’s text is accessible through the innerHTML or innerText property.

► KeyValue - The sought-for text (you can use the * and ? wildcards to specify the search masks).

► TagName - This parameter is optional. You can use it to specify tag names that you would like to search in. Note that since the name of the Find method coincides with the name of the Find method added to all tested objects by TestComplete, the Page object’s method resides in the NativeWebObject namespace, that is, in your script you should call Page.NativeWebObject.Find rather than Page.Find. For code examples, see the Searching for Web Page Element Containing Specific Text blog on our AQCommunity site or the “Searching for the Element Containing the Desired Text” help topic.

When opening some pages, you may see a Login dialog where you should enter the user name and password in order to access the page or the browser may display the Information bar asking for your permission to perform certain actions requested by the page. If you test these type of pages, you need to write code that will:

► Open the page.

► Close the the Login dialog or the Information bar by simulating user actions over them.

► Wait until the page is loaded. Note that the Page.ToUrl method, which is used to open pages, does not return the execution control to the script until the specified page is loaded. In other words, it does not return the execution control until the Login dialog or Information bar is closed. To close the dialog and informative message you should simulate user actions that will close the dialog and the bar. However, you cannot do this since the ToUrl method does not return the control until the dialog and the bar are closed. To work around the problem, you can use any of the following approaches:

► Enter the page’s URL into the Address bar or into the File | Open dialog of your web browser (for example, using the Keys method).

► Use the Navigate or Navigate2 methods of the page object (this is only valid for pages displayed in Internet Explorer or a WebBrowser control).

► Call the Page.ToUrl method using the Runner.CallObjectMethodAsync method.

Most likely the script addresses web page elements by their index. TestComplete uses indexes if the element does not contain the Id or Name attribute (if any of these attributes are specified, TestComplete uses the attribute value to address the element). Using Id or Name is more reliable than using the indexes since the indexes can change from one test run to another. To work around the problem, use any of the following approaches: • In the source code of the tested web page, specify the Name or Id attribute for all controls that you need to work with from scripts. Upon doing this, you will be able to address the controls using the specified identifiers. • Use the Page(…).NativeWebObject.Find method to search for the desired control by values of its properties and attributes (innerText, innerHTML, href, src and so on).

With TestComplete you can access internal objects of Flex applications. To do this, you should compile your Flex application with the Generate accessible SWF file option enabled and make TestComplete recognize Flash elements as MSAA objects (see instructions in the previous answer). After you prepared your Flex application and the TestComplete project, switch to the Object Browser panel. The available application objects will be displayed under the '...Window("Internet Explorer_Server").Window("MacromediaFlashPlayerActiveX")' node in the Object Browser. These objects are exposed by TestComplete’s MSAA Open Applications plug-in. Note that TestComplete can only access those controls that implement the IAccessible interface. By default, not all objects in Flex applications implement this interface.