WINDEV Concepts

152 Part 4: Advanced concepts 2 Testing and debugging a WINDEV project (development computer) 2.1 Overview The test of the entire project allows you to simulate the start of the application with the executable. This allows you to test the entire application, even if it is still being developed. When a problem occurs during the execution of the project, you can start the debugger to identify and fix the problem. WINDEV includes an extensive set of application tests that can be run from the development computer: • Test and debugging of the current project in the editor. • Execution and debugging of the executable corresponding to the current project. • Debugging of an executable already run on the development computer. Remark : The test of a project can be run regardless of the current element in the editor. 2.2 Testing and debugging the current project To test a project from the editor, go to the "Project" tab, expand "Test mode" and select "Debug project" (Ctrl + F9). The editor is automatically minimized and the project is run. 2.3 Testing and debugging the executable on the development computer Some problems can only be reproduced when testing the executable in real-use conditions. This test mode allows you to debug an executable once it is installed on the development computer. In this case, the code executed comes from the libraries (and not from the code in the elements on the computer). Therefore, the code from the current project and the code from the executable may be out-of-sync: the out-of-sync code is highlighted in pink during the debug operation. This test mode is used to run a specific executable installed on the development computer and to debug it directly. For more details, see the online help. 2.4 Debugging an executable already run on the development computer Some problems can only be reproduced when testing the executable in real-use conditions. This test mode allows you to find a problem that only occurs at runtime (and not in test mode). The principle is simple: • The developer starts the executable on their computer and directly goes to the desired location in the application. • In WINDEV, the developer opens the project that correspond to the executable and establishes a connection with it. • The WINDEV debugger monitors the execution of the program step by step. In this case, the code executed comes from the libraries (and not from the code in the elements on the computer). Therefore, the code from the current project and the code from the executable may be out-of-sync: the out-of-sync code is highlighted in pink during the debug operation. For more details, see the online help.