PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Running the test of the current window
  • Note: Minimizing (or not) the editor during the test
  • Test in a simulator
  • Stopping the test of a window
  • Changing the test of a window into automatic test
  • Notes
  • Directory of the files used for test
  • Managing the passwords (analysis or file)
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
Running the test of a single window allows you to run the current window in WINDEV or WINDEV Mobile. This allows you to run the test of your project from a given window or to check the operating mode of a window as soon as its development is ended.
If the test of the window triggers no error, ti can be transformed into an automatic test script for the window.
Like for the project test, the debugger can be started as soon as a problem occurs.
How to proceed?

Running the test of the current window

To run the test of the current window from the editor, select "Code .. Run the window test" (or [F9]). The editor is automatically minimized and the window is run.To run the test of the current window from the editor:
  • WINDEV click among the quick access buttons. The editor is automatically minimized and the window is run.
  • WINDEV Mobile click among the quick access buttons. The editor is automatically minimized and the window is run in a simulator.
When running the test of a window, the following processes are run:
  • declaring the classes,
  • initializing the project,
  • declaring the global variables of the current window,
  • initializing the controls found in the current window,
  • initializing the current window,
  • the current window takes focus,
  • entering the first control of the current window (if this control has an entry process).
During the test, all the window features can be run. You will have the ability to open other windows for example.
Notes:
  • To run the test of a window that expects one or more parameters, a default value must be given to the parameters in their declaration. Otherwise, a window is displayed, allowing you to enter the expected parameters. See Running the test of a window with parameters for more details.
  • Versions 21 and later
    WINDEV If interface modifications have been made during the window test (resizing controls, modifying their position, ...), at the end of the test, the window editor proposes to modify the interface of the corresponding window. See Using the GUI modification during a window test for more details.
    New in version 21
    WINDEV If interface modifications have been made during the window test (resizing controls, modifying their position, ...), at the end of the test, the window editor proposes to modify the interface of the corresponding window. See Using the GUI modification during a window test for more details.
    WINDEV If interface modifications have been made during the window test (resizing controls, modifying their position, ...), at the end of the test, the window editor proposes to modify the interface of the corresponding window. See Using the GUI modification during a window test for more details.
  • Versions 21 and later
    The last test run (window, query, report, ...) can be re-run from any project element via "GO .. Re-run the last test" found in the quick access buttons.
    New in version 21
    The last test run (window, query, report, ...) can be re-run from any project element via "GO .. Re-run the last test" found in the quick access buttons.
    The last test run (window, query, report, ...) can be re-run from any project element via "GO .. Re-run the last test" found in the quick access buttons.
Versions 18 and later

Note: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "Options of code editor".
  2. In the "Debugger" tab, uncheck "Minimize the editor in test mode".
  3. Validate.
New in version 18

Note: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "Options of code editor".
  2. In the "Debugger" tab, uncheck "Minimize the editor in test mode".
  3. Validate.

Note: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "Options of code editor".
  2. In the "Debugger" tab, uncheck "Minimize the editor in test mode".
  3. Validate.
AndroidiPhone/iPadWindows MobileUniversal Windows 10 App

Test in a simulator

For a Windows Mobile, Android, iOS ou Windows Store App application, WINDEV Mobile allows you to run the test of the window (and application) on the development computer via the simulation mode. This test simulates a device of the platform used on the development computer. This test is useful when no device (Android or Windows Mobile) or Mac computer can be used by the developer to compile the iOS application. However, some features are not available in simulator mode.

Stopping the test of a window

Several methods can be used to stop the test:
  • 1st method: Close the application whose test is currently run. WINDEV displays the editor that was used at the beginning of test.
  • 2nd method: Go back to the editor with the taskbar or with [Alt] + [Tab] and confirm the ending of the test. WINDEV displays the editor that was used at the beginning of test.

Changing the test of a window into automatic test

If the test of the window is completed without error, you have the ability to save the operations performed during the test in an automatic test:
  1. When going back to the editor, click .
  2. The automatic test is automatically added to your project. The description window of the automatic test is displayed.
  3. Specify the name of the test and its description if necessary.
  4. Validate.
Note: If a window is opened from the initialization code of project, a test is also created for this window. The "Automatic test" code of the project is modified to take the test of this window into account.
Notes

Directory of the files used for test

To configure the data files used when running the test of the application in the editor:
  1. Display the project description ("Project .. Project description").Display the project description: on the "Project" pane, in the "Project" group, click "Description".
  2. In the "File" tab, select the location of the test files:
    • Current directory: The data files will be found in the EXE sub-directory of the project.
    • Specific directory: The data files will be found in the specified directory.

Managing the passwords (analysis or file)

No password is requested when running the test of the window, regardless of whether the window is associated with a password-protected analysis or with a password-protected file.
The necessary passwords must be specified by programming in the initialization code of the project:
  • If the window handles a file found in a password-protected analysis, this password must be specified in HOpenAnalysis.
  • If the window handles one or more password-protected files, this password must be specified in HPass.
If the passwords are not specified in the initialization code of the project, a WLanguage error occurs when running the window test.
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment