|
- Overview
- How to proceed?
- Running the test of current dynamic page or dynamic AWP page
- Treatments performed
- Stopping the test of a dynamic page or dynamic AWP page
- Notes
- Directory of data files used for test
- Managing passwords (analysis or data file)
- Checking the runtime environment before the test
Running the test of a dynamic page or the test of a dynamic AWP page
The test of a single page allows you to run the current page in WEBDEV. This allows you to run the test of your project from a given page or to check the operating mode of a page as soon as it is fully developed. The debugger can be started during this test. Running the test of current dynamic page or dynamic AWP page To run the test of the current dynamic page from the editor: - Click on
 among the quick access buttons (or F9). - The editor is automatically minimized and the page is run in the default browser.
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. The choice of the default browser can also be performed in the WEBDEV options.
The test browser can be selected on the "Project" pane, in the "Test mode" group, by expanding "Test mode" and by selecting "Test browser". Remarks: - When running the test of a page that expects one or more parameters, a window for entering the parameters is automatically displayed.
- To start the debugger, all you have to do is use the STOP keyword in the code or a breakpoint.
 Versions 21 and laterThe 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 21The 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.
Treatments performed When running the test of a dynamic page, the following processes are run: - Declaring the classes (server code)
- Initializing the project (server code)
- Global declarations of the current page (server code)
- Initializing the controls found in the current page (server code)
- Initializing the current page (server code)
- Loading the current page (browser code)
- Entering the first control of current page (if this control has an entry process) (browser code)
When running the test of a dynamic AWP page, the page is run with an URL containing the parameters of the page and the command line of the project. The command line of the project is defined on the "Project" pane, in the "Test mode" group, by expanding "Test mode" and by selecting "Configure the test mode". The following processes are run: - Declaring the classes (server code)
- Initializing the project (server code)
- Global declarations of the current page (server code)
- Initializing the controls found in the current page (server code)
- Initializing the current page (server code)
- Loading the current page (browser code)
- Entering the first control of current page (if this control has an entry process) (browser code)
During the test: - the initialization codes (project, classes, sets of procedures, ...) are re-run whenever an action is performed in the AWP page and whenever a new AWP page is displayed.
- All the features of the page can be run. You will have the ability to open other pages for example. When going from a page to another one (PageDisplay for example), the debugger locks the execution of the next page as long as the previous page has not been entirely traced.
- InTestMode returns True.
Stopping the test of a dynamic page or dynamic AWP page Several methods can be used to stop the test: - 1st method: Close the site whose test is currently run. WEBDEV displays the editor that was used at the beginning of test.
- 2nd method: Go back to the editor with the taskbar (or Alt + Tab) and confirm that the test must be stopped. WEBDEV displays the editor that was used at the beginning of test.
Directory of data files used for test To configure the data files used when running the application test in the editor: - Display the project description: on the "Project" pane, in the "Project" group, click "Description".
- In the "File" tab, select the location of the test files:
- Current directory: The data files will be found in the EXE sub-directory of project.
- Specific directory: The data files will be found in the specified directory.
Managing passwords (analysis or data file) No password is requested during the test of the dynamic page, no matter whether the page is associated with an analysis protected at run time or with a password-protected data file. The necessary passwords must be specified by programming in the initialization code of the project: - If the page handles a file from a password-protected analysis, this password must be specified in HOpenAnalysis.
- If the page handles one or more password-protected files, this password must be specified in HPass.
If the passwords are not specified in the initialization code of project, a WLanguage error occurs during the page test. Versions 15 and laterChecking 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: 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: 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 15Checking 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: 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: 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: 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: 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. |
|
|
| |
| Click [Add] to post a comment |
|
| |
|
| |
| |
| |
| |
| |
| |
| | |
| |