|
|
|
|
|
|
|
|
|
|
- Overview
- 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
- Notes
- Different modules started automatically when testing a WEBDEV website (session/AWP mode)
- Test browser
- Testing a site from a phone
- Vista and UAC: Test launched
- Directory of the data files used for testing
- 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: Project testing can be launched 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 website (session/AWP mode) from the editor: - On the "Proyecto" tab, in the "Modo de prueba" group, expand "Modo de prueba" 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 Back button. Stopping the project test There are multiple methods to stop the test: - Method 1: Close the browser in which the test is being performed. WEBDEV displays the editor open when the test was started.
- Method 2: 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 website (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.
If the web server is not started, the test cannot be run. - The WEBDEV administrator (WD300Admin.EXE).
The administrator allows managing connections to the Web server and configure sites in WEBDEV session mode. - The WEBDEV engine (WD300AWP.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 website.
Test browser To select the test browser: - On the "Proyecto" tab, in the "Modo de prueba" group, expand "Modo de prueba".
- Select "Test browser" and choose the desired browser.
Note: The default browser is defined in WEBDEV options: - On the "Inicio" tab, in the "Entorno" group, expand "Opciones" and select "WEBDEV general options".
- In the window of WEBDEV options, click the "Web" tab. For more details, see WEBDEV options.
Tip: To select the browser used for project testing, use the project test icon among the quick access buttons. The arrow on the right expands a menu to choose the browser to be used for the test. Testing a site from a phone You can test WEBDEV websites directly from a phone. This allows you to see how the site behaves on a given screen size. To test a project on a phone: - Expand in the quick access buttons.
- In the list that appears, select "Test browser .. Phone (via a QR Code)".
- Run the test of the project by clicking the "GO" icon.
- A window with a QR code is displayed.
- Scan the QR code with the device.
- The project appears on the phone.
Remarks: - 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 usual debugging modes are available: step-by-step mode, viewing and modifying variable contents, etc.
Vista and UAC: Test launched Vista with UAC (user account control) enabled: If WEBDEV is run as administrator (context menu option or "Run this program as administrator" checkbox in executable properties), the guest account used by IIS 7 must be part of the administrator group.. Otherwise, an error is displayed in the browser. Vista without the UAC system enabled: If the Vista user is an administrator, or a user in 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 the data files used for testing To configure the data files used when running the site test in the editor: - Open the project description: On the "Proyecto" tab, in the "Proyecto" group, click "Descripción".
- On the "Files" tab, select the location of test data files:
- Current directory: Data files will be located in the project's EXE subdirectory.
- Specified directory: the data files will be located 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 prompts you to: - "Diagnose" opens the detailed diagnosis window.
- "Run 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 "Fix" button allows you to automatically solve the issue. The "Help" button will be enabled if an additional help is available. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|