With TestComplete, you can create automated tests for applications created with Electron. TestComplete recognizes web pages that implement the application interface and individual web elements on those pages, and you can simulate user actions against these web elements.
|Note:||To learn how to test applications built with Chromium Embedded Framework (CEF), see About Support for Chromium Embedded Framework.|
TestComplete can test 32- and 64-bit desktop applications created with Electron version 1.8.2.
An active license for the TestComplete Web Module.
|Note:||The license for the Desktop module is not required.|
The following plugins must be enabled in TestComplete:
Chromium Embedded Framework Support
These plugins are installed and enabled automatically as part of the TestComplete Web module. You can check whether these plugins are active in the File > Install Extensions dialog (you can find them in the Web group).
Your tested Electron application must be compiled as a binary executable file.
To simulate user actions against your Electron applications, you access web pages that the embedded Chromium web browser renders. To expose Chromium content in your Electron application:
In your TestComplete project, add your application’s binary executable to the Tested Applications collection as a Generic Windows application:
Specify the path to the binary executable of your Electron application.
If your Electron application is distributed via installable binaries, several executables can be generated upon installation. For TestComplete to be able to access the application internals, use the application’s actual executable rather than the application launcher. Typically, the needed executable is located in the %APPDATA%\Local\<Your_App_Name>\app-N.N.N folder.
To make sure that you add a proper executable to your project:
Launch your Electron application.
In TestComplete, switch to the Object Browser and locate your application in the object hierarchy tree.
Right-click the application’s
Process node and then click Add Process to TestedApps. TestComplete will add the proper executable to your current project:
TestComplete will recognize the contents that the Chromium web browser renders the same way it recognizes any other web application:
Page objects correspond to the rendered web pages. Child objects of the
Page correspond to web elements on the page. Their hierarchy depends on the web object model enabled for your current project in TestComplete (Tree, by default).
For web elements, TestComplete provides properties and methods that you can use to retrieve data of the elements and simulate user actions against them. In addition, TestComplete provides access to all native methods and properties of the web elements. You can use these native methods and properties to access data and simulate user actions that are not available through methods and properties that TestComplete provides.
You test Electron applications by simulating user actions against these web elements. You do it the same way you do it in regular web browsers.
Testing web pages in Electron applications differs from testing regular web browsers:
Page objects are nested under the
Process node of the application.
For more information on differences between regular and embedded browsers, see the Specifics of Web Testing in Embedded Browsers section in the Considerations for Web Testing topic.
With TestComplete, you can record and play back user actions in Electron applications, or you can create tests manually from scratch. Usually, it is easier to record the test first and then modify and enhance the recorded test.
When you record a test, you interact with the tested Electron application as an end-user would: navigate through the application’s screens, fill out forms and so on. TestComplete captures all actions you perform in the application and adds them to the test.
A test consists of a sequence of operations that define various interactions with objects in the tested application. For example, you can see in the sample test below that selecting an item from a combo box is represented by the
ClickItem operation, text input into text boxes - by the
SetText operation, and so on.
var orderFrm = Aliases.orders.pageOrders.formOrder;
var textboxCustomerName = orderFrm.textboxCustomerName;
def Test_OrdersElectron(): TestedApps.Orders.Run(); orderFrm = Aliases.orders.pageOrders.formOrder; orderFrm.selectProduct.ClickItem("FamilyAlbum"); textboxCustomerName = orderFrm.textboxCustomerName; textboxCustomerName.Click(27, 12); textboxCustomerName.SetText("John Smith"); orderFrm.SubmitOrderbutton.Click();
Set orderFrm = Aliases.orders.pageOrders.formOrder
Set textboxCustomerName = orderFrm.textboxCustomerName
Call textboxCustomerName.Click(27, 12)
var orderFrm, textboxCustomerName;
orderFrm := Aliases.orders.pageOrders.formOrder;
textboxCustomerName := orderFrm.textboxCustomerName;
var orderFrm = Aliases["orders"]["pageOrders"]["formOrder"];
var textboxCustomerName = orderFrm["textboxCustomerName"];
The recorded tests can be modified and enhanced in a number of ways to create more flexible and efficient tests. For example, you can:
Add new operations, reorder operations and modify their parameters.
Delete or disable unneeded operations (for example, superfluous recorded operations).
Insert checkpoints for verifying objects and values in the tested application.
Create data-driven tests that run multiple test iterations using different sets of data.
Refer to the following topics to learn more about creating and enhancing tests:
|Creating tests using recording||Recording Tests|
|Creating tests manually||Keyword Testing and Scripting|
|Simulating user actions||Working With Application Objects and Controls|
|Running tests||Running Tests|
|Launching applications automatically at the beginning of the test run||Adding Tested Applications and
Running Tested Applications
|Creating checkpoints for verifying application behavior and state||Checkpoints|
|Running multiple test iterations using data from an external file||Data-Driven Testing|
There are several ways to refer to objects in Electron applications:
By default, when you record a test, TestComplete automatically adds recorded objects to the Name Mapping repository in your project and uses names it assigns to mapped objects (such names are called aliases) to refer them in tests. You can see mapped objects and their aliases in the Name Mapping editor: