Starting with version 12.1, the DevExpress WinForms controls provide Coded UI Tests support. This article answers frequently asked questions related to CUIT support in our controls, licensing issues and troubleshooting solutions.
Officially, we support Coded UI Test Extension and recommend using it to create automated tests for our desktop components. However, according to the recent Microsoft announcements (see Visual Studio 2019 Preview Release Notes), Visual Studio 2019 will be the final version of Visual Studio with Coded UI test features. According to Microsoft's recommendations, you can use Selenium for testing web-applications and Appium with WinAppDriver for testing desktop and UWP apps. Although we don't declare official support for these testing tools, our research showed that these testing tools can be used with our components.
1) What is the Coded UI Test Extension?
The**Coded UI Test Extension** for DevExpress WinForms controls is an extension to Microsoft CUIT tailored to facilitate UI testing in DevExpress WinForms controls using the Microsoft CUIT framework. Refer to the Microsoft CUITarticle to learn how to record your first UI test.
2) How can I get Coded UI tests to work with DevExpress WinForms controls? Should I install a specific extension to get it to work?
Yes. For Coded UI Tests to recognize our controls, you need to install the DevExpress Coded UI Test Extension (CUIT Extension) for WinForms Controls, shipped as a part of the Universal subscription.
3) What controls and actions does the DevExpress CUIT Extension support?
There are four levels of Coded UI support. All DevExpress WinForms controls provide support for Microsoft Coded UI Tests (CUIT) level 1. The list of controls that support level 2 and higher is available in the Coded UI Test Extension: Supported Controls and Actions help topic.
4) What IDE and tools do I need to use the DevExpress CUIT Extension?
It is necessary to use Microsoft Visual Studio 2010 Premium/Ultimate/Test Professional edition (Service Pack 1), Microsoft Visual Studio 2012 Premium/Ultimate/Test Professional edition, Microsoft Visual Studio 2013 Premium/Ultimate/Test Professional edition, or Microsoft Visual Studio 2015 Enterprise edition. Refer to the Coded UI Test Extension: System Requirements help topic for more information.
5) What subscription do I need to use the CUIT Extension?
The CUIT Extension is a part of the Universal subscription. With other subscriptions, the CUIT Extension can be installed in Trial mode. So, you can test them even if you don't have the Universal subscription.
6) I do not develop applications, I only test applications using your controls. Should I have a separate Universal subscription to create Coded UI tests for these applications?
To use the CUIT Extension on a test machine, you need to have a separate valid Universal license for each tester.
If you do not have Visual Studio installed on a test machine and use Microsoft Test Manager to build and run tests, you also need to have a separate license for each tester to use the CUIT Extension.
For more information about the CUIT Extension licensing policy, contact us at email@example.com.
7) Do you have an installer that only installs the CUIT Extension, so that I can use it on a test machine without installing your controls?
For Universal subscription owners, a separate installer for the CUIT Extension is available. You can download it from the Download Manager.
As mentioned above, the .NET Controls and Libraries installer also installs the CUIT Extension.
So, there is no need to run a separate installer for the CUIT Extension on a machine where .NET Controls are already installed.
For more information on the CUIT Extension installer, refer to Julian Bucknall’s blog post: Separate Installation of Coded UI Test Extension for WinForms Controls
8) How can I check to see if the extension is registered properly?
When you create a new Coded UI test, the CUIT Extension assembly should automatically be added to the project's References section.
9) I can't get your extension to work. What should I do?
First, ensure that your system meets the System Requirements for the CUIT Extension.
If you installed Visual Studio after installing the CUIT Extension, run the CUIT Extension installation again in Repair mode.
The minor version of the CUIT Extension must be the same as the minor version of the DevExpress WinForms controls used in your application, or installed on the test machine. However, you can still use multiple major versions on a single machine.
All installation processes are written to an installation log file. For.NET products, it is located in the .NET Controls and Libraries installation folder you specified during the installation. For the separate Coded UI Test Extension installer, the path is %ProgramFiles%\DevExpress XX.Y\DevExpressCodedUIExtensions. If you have any issues, refer to that file to view the errors that occurred during installation.
If the information above doesn't help, please run the attached BAT file, which will collect more information about your system. Send us the generated log file so that we can research this issue.
10) How can I check if your controls are recognized properly?
When you create an Assert method, the Technology property in the PropertyGrid should display "DevExpress". In addition, all classes generated for the DevExpress WinForms controls should start with the "DX" prefix.
11) I copied the assembly with the CUIT Extension on my machine and added a reference to it in the project References section, but DevExpress WinForms controls are not recognized properly. Why?
The CUIT Extension should be installed to the GAC and registered in a special manner on your machine. The .NET Controls and Libraries and the separate Coded UI Test Extension installers do this automatically. Please refer to the “Hello, World” Extension for Coded UI Test blog post to learn more on how to register a custom CUIT Extension.
Show all comments