WEBDEV Concepts

198 Part 6: Testing a Web site 3 Testing a remote WEBDEV site Several methods can be used to run a test and to debug a site on the development computer. However, in some cases, you may have to debug the site directly on the user computers. From your office in London, you have the ability to debug a site running on a Web server in Taiwan. The debug operation is done without having to go anywhere, on the final configuration directly. Two features are available: • Starting and debugging the site on a remote application server. • Debugging a site currently used on a remote application server. For these two features, a specific configuration of the remote computer is required. 4 Testing a page 4.1 Testing the page from the editor To test a page from the editor : 1. Open the page to be tested. 2. Click in the quick access buttons of the WEBDEV menu. You can also press F9. 3. The editor is automatically minimized and the page is run. During the test, all page features can be run. You will have the ability to open other pages for example. 4.2 Stopping the page test There are multiple methods to stop the test: • 1st method : Close the page being tested. WEBDEV displays the editor open when the test was started. • 2nd method : • Go back to the editor via the taskbar or press Alt + Tab. • Stop the test. WEBDEV displays the editor open when the test was started. 5 Tracing a project 5.1 Debugging principles Debugging an application consists in: • checking the operating mode of a process, • understanding the operating mode of an existing program, • checking the values of variables, • checking the operating mode of special cases in an application or in a site. The debugger is used to perform these operations. Remark : WEBDEV also includes several trace tools (trace window, information box, etc.). For more details, see "Debugging without debugger", page 199. 5.2 Debugger overview The debugger monitors WLanguage programs so they can be improved. The executed source code appears on the screen. The processes run are sorted in hierarchical order in the "Debugger" pane. The value of the variables is displayed: • individually in the on-hover tooltip of each variable. • in the "Debugger" pane. 5.3 Debugger features The debugger is used to: • view the call stack, • view the content of variables or expressions, • execute the code step by step with the possibility to skip code blocks, • use conditional breakpoints, • modify the code while continuing the execution, • etc.

RkJQdWJsaXNoZXIy NDQ0OA==