Recording a Windows test
You can record a Windows test to capture the actions that you perform on Windows desktop applications and on the Add-ins in Microsoft Office applications. The actions are captured as test steps in Windows tests.
Generally, when you record actions on the Windows desktop application, the controls on the
application are identified by using one of the control properties which is a unique
identifier for that control. For some of the controls on the Windows applications, when the
Name property is also available the Label
property is not generated. The Label property is generated only for the
following controls when the Name property is not available:
- Input field
- List
- Combo box
You can record actions on multiple windows including the dialogs of the Windows desktop application. You can also press Alt+Tab to navigate between the child and the main windows while recording the Windows test.
Tip:
- When you record a test on the Windows application, you must wait when the cursor is busy, and then proceed when the cursor changes to the default state.
- When the Add-in application response time is more than expected, you can press the
left Shift key twice to synchronize the application state with IBM® DevOps Test UI (Test UI). The cursor is then is
restored to the default state.
Before you can perform the next action on the Add-in application, you must click on the Add-in application once.
You can edit the generated Windows test in the test editor. For information, see Editing a Windows test.