PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
This content comes from an automatic translation.
  • Overview
  • How to?
  • Running the test of current window
  • Remark: Minimizing (or not) the editor during the test
  • Test in a simulator
  • Stopping the window test
  • Notes
  • Directory of 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.
Like for the project test, the debugger can be started as soon as a problem occurs.
How to?

Running the test of current window

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.
When a window test is launched, the following WLanguage events are executed:
  • declaring classes,
  • initializing the project,
  • declaring the global variables of 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 window features can be run. You will have the ability to open other windows for example.
Remarks:
  • 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

Remark: 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. Under "Home", in the "Environment" group, scroll down "Options" and select "Code Editor Options"..
  2. In the "Debugger" tab, uncheck "Minimize editor in test mode".
  3. Validate.
New in version 18

Remark: 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. Under "Home", in the "Environment" group, scroll down "Options" and select "Code Editor Options"..
  2. In the "Debugger" tab, uncheck "Minimize editor in test mode".
  3. Validate.

Remark: 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. Under "Home", in the "Environment" group, scroll down "Options" and select "Code Editor Options"..
  2. In the "Debugger" tab, uncheck "Minimize editor in test mode".
  3. Validate.
Universal 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 window test

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 press Alt + Tab) and confirm the end of test. WINDEV or WINDEV Mobile displays the editor that was used at the beginning of test.
Notes

Directory of files used for test

To configure the data files used when running the application test in the editor:
  1. Open the project description: under the "Project" section, in the "Project" group, click on "Description".
  2. In the "File" tab, select the location of the test files:
    • Current directory: The data files will be in the project EXE subdirectory.
    • 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 uses one or more password-protected files, this password must be specified with HPass.
If the passwords are not specified in the initialization code of the project, a WLanguage error occurs when running the window test.
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment