PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Overview
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Overview
WINDEV and WINDEV Mobile feature multiple methods to test applications:
  • Test of the entire project
    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 not complete. When a problem occurs during the execution of the project, you can start the debugger to identify and fix the problem.
    AndroidAndroid Widget iPhone/iPad The test is run in the simulator.
  • Test of a single window
    Testing a single window allows you to run the current window in WINDEV or WINDEV Mobile. 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 as soon as a problem occurs.
    AndroidAndroid Widget iPhone/iPad The test is run in the simulator.
  • Test of a single query
    Testing a single query allows you to run the current query in WINDEV or WINDEV Mobile. This allows you to check the operating mode of a query as soon as its development is complete.
  • Test of a single report
    Testing a single report allows you to run the current report in WINDEV. This allows you to check the implementation of a report as soon as it is developed. Like for the project test, the debugger can be started as soon as a problem occurs.
  • Running the project step by step
    Running the project step by step allows you to start the debugger when starting the application. This solution allows you to monitor the application progress.
  • Regression tests
    The regression tests on a project element or on the entire project enable you to check whether a modification (code, interface, and so on) does not affect the operating mode of the application. WINDEV proposes to save the tests in the project directly in order to run these tests for each new application version.
Versions 21 and later
Remarks:
  • During a debug operation, all the elements on which you stop (via an breakpoint for example) are opened in the editor. 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.
  • Versions 22 and later
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
    New in version 22
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
New in version 21
Remarks:
  • During a debug operation, all the elements on which you stop (via an breakpoint for example) are opened in the editor. 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.
  • Versions 22 and later
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
    New in version 22
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
Remarks:
  • During a debug operation, all the elements on which you stop (via an breakpoint for example) are opened in the editor. 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.
  • Versions 22 and later
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
    New in version 22
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
    The lines of code run by the different types of test are automatically taken into account by the Code coverage.
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment