Running the test of current dynamic page or dynamic AWP page

1. Select "Code .. Run the page test" (or press F9). Click among the quick access buttons (or press F9).
2. The editor is automatically minimized and the page is run in the default browser.

Tip: To select the browser used when running the page test, click the test icon of the page. The arrow on the right expands a menu allowing you to choose the browser that will be used for test.

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.

• 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 later
  The 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 21
  The 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.
  The 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.

Processes run

• Declaring the classes (server code)
• Initializing the project (server code)
• Declaring the global variables 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 the current page (if this control has an entry process) (browser code)

• Declaring the classes (server code)
• Initializing the project (server code)
• Declaring the global variables 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 the current page (if this control has an entry process) (browser code)

• 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

• 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

1. Display the project description ("Project .. Project description").Display the project description: on the "Project" pane, in the "Project" group, click "Description".
2. 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 the project.
   • Specific directory: The data files will be found in the specified directory.

Managing passwords (analysis or data file)

• 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.