WINDEV Concepts

Part 4: Advanced concepts 151 Testing an application 1 Overview WINDEV includes multiple methods to test applications: • test of the entire project, • test of a single window, • test of a single query (see the online help for more details), • test of a single report (see the online help for more details), • step-by-step project execution, • application performance test, • regression test/automatic test. By testing the project you can simulate how the application will run when launched from an executable. This allows you to test the entire application, even if it is still being developed. If a problem occurs, you can start the debugger to identify and fix the problem. The window test is used to run the current window only. This allows you to test your project from a given window or to test a window once it has been finished. Like for the project test, the debugger can be started if a problem occurs. The test of a single query runs the current query only. This allows you to check the operating mode of a query once it has been developed. The test of a single report runs the current report only. This allows you to test a report once it has been developed. Like for the project test, the debugger can be started if a problem occurs. The step-by-step project execution allows you to start the debugger when starting the application. This solution allows you to monitor the application progress. The performance test checks and optimizes the execution time of your application. The regression test (or automated test) is based on the execution of scripts. It checks that the existing features are still supported when running the applications. In addition to these methods, WINDEV also provides a "Code coverage" tool to measure how many tests have been executed on your application. For more details, see the online help.