PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
This content comes from an automatic translation.
  • Overview
  • How to proceed?
  • Testing a site in session/AWP mode (or the session/AWP portion of a site)
  • Running the test of site features
  • Stopping the project test
  • Notes
  • The different modules launched 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
Running the test of the entire project is used to simulate the start of 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 to run the project test 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 the session/AWP portion of a site)

To test a WEBDEV site (session/AWP mode) from the editor:
  1. Under the "Project" section, in the "Test mode" group, scroll down "Test mode" and select "Debug the project"..
    You also have the ability to 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 the first page is opened in project session mode, the following WLanguage events are executed:
  • declaring classes,
  • initializing the project,
  • declaration of the first page globals in session mode,
  • initializing the first page,
  • initializing the controls found in the first page,
  • loading the first page,
  • entry of the first field on the first page (if this field has a WLanguage of Input event).

Running the test of site features

We recommend that you run the test of all site features 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 test. WEBDEV displays the editor that was used at the beginning of test.
Notes

The different modules launched 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 (WD250Admin.EXE).
    The administrator can manage connections to the Web server and set up sites in WEBDEV session mode.
  • The WEBDEV engine (WD250AWP.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. Under "Project", in the "Test mode" group, unroll "Test mode".
  2. Select "Test browser" and choose the requested browser.
Remark: The default browser is defined in the WEBDEV options:
  1. Under "Home", in the "Environment" group, scroll down "Options" and select "General WEBDEV options"..
  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