PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | French EN
  • Overview
  • How to proceed?
  • Testing a site in session/AWP mode (or a part of a site in session/AWP mode)
  • Running the test of site features
  • Stopping the project test
  • Notes
  • Different modules started automatically when testing a WEBDEV site (session/AWP mode)
  • Test browser
  • Vista and UAC: Running a test
  • Directory of data files used for test
  • Checking the runtime environment before the test
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
The test of the entire project allows simulating the startup of the site. This allows you to run test of entire site, even if its development is not finished yet. As soon as a problem occurs in the project execution (server code only), the debugger can be started to identify and fix the problem.
Remark: The test of a project can be run regardless of the current element in the editor.
This help page explains how test a project from the WEBDEV editor. It is also possible to test a project corresponding to a site in session mode from the WEBDEV administrator.
For more details, see:
How to proceed?

Testing a site in session/AWP mode (or a part of a site in session/AWP mode)

To test a WEBDEV site (session/AWP mode) from the editor:
  1. On the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Debug project".
    You can also click among the quick access button or press Ctrl + F9.
  2. The editor is automatically minimized and the project is run in the default browser.
  3. The first page of the site in session mode is displayed.
At the start of the project test, before opening the first page in session mode of the project, the following WLanguage events are run:
  • declaring classes,
  • initializing the project,
  • declaring the global variables of the first page in session mode,
  • initializing the first page,
  • initializing the controls found in the first page,
  • loading the first page,
  • entering the first control of the first page (if this control has a WLanguage entry event).

Running the test of site features

It is recommended to test all the features of the site as well as the use of browser Back button. See Managing the Back button for more details.

Stopping the project test

Several methods can be used to stop the test:
  • 1st method: Close the browser in which the test is run. WEBDEV 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 the test. WEBDEV displays the editor that was used at the beginning of test.
Notes

Different modules started automatically when testing a WEBDEV site (session/AWP mode)

The following modules are automatically started during a test:
  • The Web server installed on the computer and configured for WEBDEV when installing WEBDEV Development.
    The test cannot be run if the Web server is not started.
  • The WEBDEV administrator (WD260Admin.EXE).
    The administrator allows managing connections to the Web server and configure sites in WEBDEV session mode.
  • The WEBDEV engine (WD260AWP.EXE).
    The WEBDEV engine is used to manage the requests made by the Web users from their browser and to return the corresponding dynamic HTML page.
  • The Internet browser.
    The Internet browser is used to display the HTML pages of the WEBDEV site.

Test browser

To select the test browser:
  1. On the "Project" pane, in the "Test mode" group, expand "Test mode".
  2. Select "Test browser" and choose the desired browser.
Remark: The default browser is defined in the WEBDEV options:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "General options of WEBDEV".
  2. In the window of WEBDEV options, click the "Web" tab. See WEBDEV options for more details.
Tip: To select the browser used when running the test of the page, click the test icon of the page among the quick access buttons. The arrow on the right expands a menu allowing you to choose the browser that will be used for test.

Vista and UAC: Running a test

Vista with UAC (user account control) enabled: If WEBDEV is started as administrator (option from the popup menu or "Run this program as administrator" in the properties of the executable), the guest account used by IIS7 must be part of the administrator group. Otherwise, an error is displayed in the browser.
Vista without the UAC enabled: If the Vista user is an administrator or a user from the administrator group, the guest account used by IIS 7 must be part of the administrator group. Otherwise, an error is displayed in the browser.

Directory of data files used for test

To configure the data files used when running the site test in the editor:
  1. Open the project description: on the "Project" pane, in the "Project" group, click "Description".
  2. In the "Files" tab, select the location of test data 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.
Versions 15 and later

Checking the runtime environment before the test

Before running a project test, WEBDEV checks whether the test environment is properly configured.
If a problem is detected, WEBDEV proposes to display the diagnostic window:
Proposition of diagnostic for the test environment
The available options are as follows:
  • "Start the diagnostic" opens the window for detailed diagnostic.
  • "Run the test" ignores the diagnostic and runs the test. This option must be used if the diagnostic is incorrect.
  • "Cancels" cancels the test.
The window for detailed diagnostic is as follows:
Details of the diagnostic
This window performs a set of tests to check whether the test environment is properly configured.
For each detected error, a "Correct" button is used to automatically restore the correct test environment.
The "Help" button will be enabled if an additional help is available.
New in version 15

Checking the runtime environment before the test

Before running a project test, WEBDEV checks whether the test environment is properly configured.
If a problem is detected, WEBDEV proposes to display the diagnostic window:
Proposition of diagnostic for the test environment
The available options are as follows:
  • "Start the diagnostic" opens the window for detailed diagnostic.
  • "Run the test" ignores the diagnostic and runs the test. This option must be used if the diagnostic is incorrect.
  • "Cancels" cancels the test.
The window for detailed diagnostic is as follows:
Details of the diagnostic
This window performs a set of tests to check whether the test environment is properly configured.
For each detected error, a "Correct" button is used to automatically restore the correct test environment.
The "Help" button will be enabled if an additional help is available.

Checking the runtime environment before the test

Before running a project test, WEBDEV checks whether the test environment is properly configured.
If a problem is detected, WEBDEV proposes to display the diagnostic window:
Proposition of diagnostic for the test environment
The available options are as follows:
  • "Start the diagnostic" opens the window for detailed diagnostic.
  • "Run the test" ignores the diagnostic and runs the test. This option must be used if the diagnostic is incorrect.
  • "Cancels" cancels the test.
The window for detailed diagnostic is as follows:
Details of the diagnostic
This window performs a set of tests to check whether the test environment is properly configured.
For each detected error, a "Correct" button is used to automatically restore the correct test environment.
The "Help" button will be enabled if an additional help is available.
Minimum version required
  • Version 10
Comments
Click [Add] to post a comment