PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
WINDEV and WINDEV Mobile propose several methods for running the test of your applications:
  • Test of entire project
    The test of the entire project is used to simulate the start of the application by the executable. This allows you to run the test of the entire application, even if its development is not finished yet. As soon as a problem occurs in the project execution, the debugger can be started to identify and fix the problem.
    AndroidAndroid Widget iPhone/iPadWindows Mobile The test is run in the simulator.
  • Test of a single window
    Running the test of a single window allows you to run the current window in WINDEV or WINDEV Mobile. This allows you to run the test of your project from a given window or to check the operating mode of a window as soon as its development is ended. Like for the project test, the debugger can be started as soon as a problem occurs.
    AndroidAndroid Widget iPhone/iPadWindows Mobile The test is run in the simulator.
  • Test of a single query
    Running the test of 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 ended.
  • Test of a single report
    Running the test of 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 launching the application. This solution allows you to monitor the progress of the application.
  • 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
Notes:
  • 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 code lines run by the different types of test are automatically taken into account by the Code coverage.
    New in version 22
    The code lines run by the different types of test are automatically taken into account by the Code coverage.
    The code lines run by the different types of test are automatically taken into account by the Code coverage.
New in version 21
Notes:
  • 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 code lines run by the different types of test are automatically taken into account by the Code coverage.
    New in version 22
    The code lines run by the different types of test are automatically taken into account by the Code coverage.
    The code lines run by the different types of test are automatically taken into account by the Code coverage.
Notes:
  • 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 code lines run by the different types of test are automatically taken into account by the Code coverage.
    New in version 22
    The code lines run by the different types of test are automatically taken into account by the Code coverage.
    The code lines run by the different types of test are automatically taken into account by the Code coverage.
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment