TestComplete supports testing of various AngularUI controls. You can also modify project properties so that TestComplete recognizes your custom AngularUI controls. The sections below describe how you can test AngularUI controls in detail.
About Testing AngularUI Controls
TestComplete can work with any web control via the control’s graphical user interface displayed in a web browser, no matter how the control is implemented on the server side. You can test web applications that use controls implemented by using various technologies and frameworks, including Angular frameworks and component libraries (like AngularUI, Angular Material, and etc.).
Besides, TestComplete provides extended support for most of AngularUI controls. It automatically associates them with special scripting test objects that contain supplementary methods and properties for working with the controls, for example, for selecting individual items and retrieving the item text.
Support for AngularUI controls is rather transparent. During test recording, TestComplete automatically recognizes AngularUI controls on a page and records the appropriate test commands for your actions. You can then run the recorded test to see how TestComplete simulates user actions on the controls. The entire procedure is very similar to recording and running web tests that work with “regular” web controls. See Web Testing Tutorial, then try to record and run tests on your AngularUI web pages.
Why my control may be missing from the Object Browser
There can be a situation when your AngularUI control is recognized by TestComplete but is excluded from the object hierarchy of your tested application (the hierarchy you can explore with the Object Browser or the Object Spy). This happens because TestComplete excludes custom web elements that do not have a role assigned to them or do not have text contents. To learn more about it, see Web Elements Included in and Excluded From the Object Hierarchy. To avoid the issue, make sure that your tested control has either the role assigned to it in the application source code or has the non-empty text content.
Below is a full list of the AngularUI controls for which TestComplete provides extended support.
|AngularUI Bootstrap Accordion||AngularUI Bootstrap 1.1.2 and later||.panel-group|
|AngularUI Bootstrap Alert||AngularUI Bootstrap 1.1.2 and later||.alert|
|AngularUI Bootstrap Button||AngularUI Bootstrap 1.1.2 and later||.btn|
|AngularUI Bootstrap Button Group||AngularUI Bootstrap 1.1.2 and later||.btn-group|
|AngularUI Bootstrap Carousel||AngularUI Bootstrap 1.1.2 and later||.carousel|
|AngularUI Bootstrap Checkbox||AngularUI Bootstrap 1.1.2 and later||.btn|
|AngularUI Bootstrap Datepicker||AngularUI Bootstrap 1.1.2 and later||.uib-datepicker|
|AngularUI Bootstrap Dropdown||AngularUI Bootstrap 1.1.2 and later||.dropdown-toggle|
|AngularUI Bootstrap Modal||AngularUI Bootstrap 1.1.2 and later||.modal|
|AngularUI Bootstrap Pills||AngularUI Bootstrap 1.1.2 and later||.nav-pills|
|AngularUI Bootstrap Radio Button||AngularUI Bootstrap 1.1.2 and later||.btn|
|AngularUI Bootstrap Split Button||AngularUI Bootstrap 1.1.2 and later||.btn-group .btn-group-vertical|
|AngularUI Bootstrap Tabs||AngularUI Bootstrap 1.1.2 and later||.nav-tabs|
|AngularUI Bootstrap Timepicker||AngularUI Bootstrap 1.1.2 and later||.uib-timepicker|
|AngularUI Bootstrap Toggle Button||AngularUI Bootstrap 1.1.2 and later||.btn|
|AngularUI Calendar||AngularUI Calendar 1.0.0 and later||.calendar|
|AngularUI Date||AngularUI Date 1.0.0 and later||.hasDatepicker|
|AngularUI Grid||AngularUI Grid 3.1.1 and later||.ui-grid-render-container|
|AngularUI Select||AngularUI Select 0.14.9 and later||.ui-select-container .ui-select-multiple|
|AngularUI Slider||AngularUI Slider 0.2.1 and later||.ui-slider|
Note: If your control is not in the list, you can try working with it by using the properties and methods TestComplete provides for standard web elements. See Support for Web Controls.
Supported Browser Versions
TestComplete supports testing of AngularUI controls in web applications displayed in the following browsers:
Microsoft Internet Explorer ver. 11.
Note: Starting from TestComplete version 14.70, TestComplete does not support recording web tests in the non-Chromium version of Edge.
Mozilla Firefox ver. 78 ESR, 79 - 85.
If you use a later version of Firefox, check whether a patch is available for it.
Google Chrome ver. 88.
If you have a TestComplete version earlier than 12.42, your version of the SmartBear Test Extension will be incompatible with newer versions of the Chrome web browser. To test web applications in Chrome 88, you will have to upgrade your TestComplete to some later version. We recommend using version 14.73.
If you use a later version of Google Chrome, check whether a patch is available for it.
Any web browser based on the Microsoft WebBrowser control.
Note: The Edge-based WebBrowser control is not supported.
Embedded Chromium web browser:
In applications built with Chromium Embedded Framework (CEF) version 85.0.4183 and earlier (except CEF3 1750).
Note: For CEF applications that use WPF controls, only versions 84.0.04147 and earlier are supported.
In applications built with Electron version 1.8.2, 2.0.2, 3.0.2, 4.0.2, 5.0.0, 6.0.0, 6.1, 7.0.0, 7.1, 8.0 - 8.1, 9.2.0, 10.1.0.
A license for the Web module of TestComplete.
The AngularUI Control Support plugin. It provides access to controls via special program objects.
The following plugins:
Web Testing - Implements web testing, enables testing of web applications running in Internet Explorer, Edge or WebBrowser control (but not the Edge-based WebBrowser control).
Firefox Support - Enables testing of web applications running in Mozilla Firefox.
Chrome Support - Enables testing of web applications running in Google Chrome.
Chromium Embedded Framework Support - Enables web testing in applications created with Chromium Embedded Framework (CEF) or with Electron.
All these plugins are installed and enabled automatically.
If you experience issues when working with the controls, select File | Install Extensions from the main menu of TestComplete to check whether the plugins are active. If a plugin is not available, run the TestComplete installation in the Repair mode.