- How to?
- 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
- Different modules started automatically when testing a WEBDEV site (session/AWP mode)
- Test browser
- Testing a site from a phone
- Vista and UAC: Running a test
- Directory of data files used for test
- Checking the runtime environment before the test
Testing a dynamic project (session or AWP mode) from WEBDEV
The test of the entire project allows simulating the startup of the site. This makes it possible to test the entire site, even if its development is not complete 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:
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:
- On the "Project" tab, in the "Test mode" group, expand "Test mode" and select "Debug project".
You can also click in the quick access buttons or press Ctrl + F9.
- The editor is automatically minimized and the project is run in the default browser.
- 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. For more details on the browser's back button, see Managing the Back button
Stopping the project test
There are multiple methods to stop the test:
- 1st method: Close the browser in which the test is run. WEBDEV displays the editor open when the test was started.
- 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 open when the test was started.
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 (WD280Admin.EXE).
The administrator allows managing connections to the Web server and configure sites in WEBDEV session mode.
- The WEBDEV engine (WD280AWP.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 displays the HTML pages of the WEBDEV site.
To select the test browser:
- On the "Project" tab, in the "Test mode" group, expand "Test mode".
- Select "Test browser" and choose the desired browser.
: The default browser is defined in the WEBDEV options:
- On the "Home" tab, in the "Environment" group, expand "Options" and select "General options of WEBDEV".
- In the window of WEBDEV options, click the "Web" tab. For more details, see WEBDEV options.
: To select the browser used when running the test of the page, click the test icon of the page in the quick access buttons. The arrow on the right expands a menu allowing you to choose the browser that will be used for test.
New in version 28
Testing a site from a phone
You can test WEBDEV sites directly from a phone. This allows you to see how the site behaves on a given screen size.
To test a page on a phone:
- Expand the page test icon in the quick access buttons.
- In the list that appears, select "Test from a phone (access via a QR Code)".
- Scan the QR Code with the phone.
- The page appears on the device.
To test a project on a phone:
- Expand the project test icon in the quick access buttons.
- In the list that appears, select "Test browser .. Phone (via a QR Code)".
- Scan the QR Code with the phone.
- The project appears on the phone.
- Simply make sure the mobile device is connected to the same network as the PC (generally, the Wi-Fi network of your organization).
- Breakpoints are enabled. The standard debug mode is still available: step-by-step execution, ability to view and modify the content of variables, etc.
Vista and UAC: Running a test
Vista with UAC (user account control) enabled: If WEBDEV is started as administrator (option in the context 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:
- Open the project description: on the "Project" tab, in the "Project" group, click "Description".
- 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.
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 displays a dialog box to open the diagnostic window:
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.
- "Cancel" cancels the test.
The window for detailed diagnostic is as follows:
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.