Creating an automated test on a window

1. Open the window whose test must be run in the window editor.
2. On the "Automated tests" tab, in the "Tests" group, expand "New" and select "Record a new scenario".
   • An information dialog is displayed, indicating that the window will be run in test mode and that all the operations performed from now on will be recorded in WLanguage in the test scenario.
   • Click the "Start recording" button to validate.
     Note: If the window is a parameterized window, enter the window's test values.
3. Perform the necessary operations in your window.
4. To stop the test, close the window.
5. At the end of the test, the test description window is displayed. You have the ability to specify the test name and its description ("General" tab). The information available on the other tabs is specified by default. This information can be modified at any time.
6. The code corresponding to the test is displayed in the code editor.

Remarks

• If a window is opened from the "Initialization" event of the project, a test is also created for this window. The event "Automated test" of the project is modified to take into account the test of this window.
• If your application uses the User Groupware:
  • in manual mode: if function gpwOpen is used, this function must be replaced by function gpwLogin in the test code.
  • in automatic mode: in the user groupware configuration window, specify the login and password to be used for automatic test mode.
• If the window whose test is run opens another window (or an internal window), the operations performed in the different windows are recorded in the same scenario.
• If the window opens another window found in a component, the operations performed in the component window will also be recorded in the same scenario.

Limits

• No test can be run on the Carousel control.
• No test can be run on the windows automatically displayed by WINDEV (windows for managing HFSQL errors, print windows, ...). If these windows are included in the project in order to be customized, the automated test can be run.
• The operation used to Drag and Drop a control to another one cannot be replayed in an automated test.
• The recording of a scenario ignores the persistence of controls. Indeed, if this was not the case, the context and therefore the result could be different between two tests passed at two different moments.
• When an automated test is run on an organizer control, the selection of the period with the mouse must be performed without scroll.
• You cannot run the test of a print via the print preview. The code automatically generated to manage the "Preview" window must be deleted from the test code.