PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Running the test of the current report
  • Note: Minimizing (or not) the editor during the test
  • Stopping the test of a report
  • Notes
  • Directory of the files used for test
  • Managing passwords (analysis or data file)
  • Special case for WINDEV Mobile: Opening a window in test mode in the code of the project
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
The test of a single report allows you to run the current report in WINDEV, WEBDEV or WINDEV Mobile. Like for the project test, the debugger can be started as soon as a problem occurs.
Note: The test of the report is run on the development computer only. The data used for test corresponds to the data found on the development computer.
The following processes are run during the test of a report:
  • Initialization process of project.
  • Processes associated with the report.
  • Processes associated with the report blocks.
  • Processes associated with the report controls.
Note: The test of the report is available for the reports based on a query, a data file, a text file and for the reports associated with no data source. For the other types of reports, you must run the test of the element (window, page or project) from which the report is printed.

Important

During the test of a report in Reports & Queries, the initialization process of the project is run.
Versions 18 and later
iPhone/iPad This feature is now available for the iPhone/iPad projects.
New in version 18
iPhone/iPad This feature is now available for the iPhone/iPad projects.
iPhone/iPad This feature is now available for the iPhone/iPad projects.
How to proceed?

Running the test of the current report

To run the test of the current report:
  1. Click .Click Go among the quick access buttons (F9 key).
  2. A screen allows you to choose the print mode of the report:
    Print Mode
    The available options are:
    • Print preview: used to preview the report as it will be printed.
    • Printer: the report is directly printed onto the default printer.
    • HTML file: the report is saved in an HTML file and displayed in the Internet browser installed on the computer.
    • RTF file: the report is saved in an RTF file and displayed in a text editor (Word for example).
    • PDF file: the report is saved in a PDF file and displayed in a PDF viewer (Acrobat Reader for example).
    • Versions 17 and later
      Generic PDF file: the report is saved in a generic PDF file (independent of the printer) and displayed in a PDF viewer (Acrobat Reader for example).
      New in version 17
      Generic PDF file: the report is saved in a generic PDF file (independent of the printer) and displayed in a PDF viewer (Acrobat Reader for example).
      Generic PDF file: the report is saved in a generic PDF file (independent of the printer) and displayed in a PDF viewer (Acrobat Reader for example).
    See Print modes of report for more details.
  3. Choose the print mode and validate. If your report is not saved, WINDEV, WEBDEV or WINDEV Mobile automatically proposes to save it under the name given in the wizard for report creation.
  4. Specify the additional information if necessary:
    • If the report is bounded, a window allows you to enter the report bounds. See Bounded report for more details.
    • If the report is based on a query with parameters, a window allows you to enter the query parameters. See Report on query with parameters for more details.
    • If the report expects parameters, give a default value to the parameters in the declaration of parameters. See Passing parameters to a report for more details.
Versions 21 and later
Note: 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.
Run the test again
New in version 21
Note: 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.
Run the test again
Note: 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.
Run the test again
Versions 18 and later

Note: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "Options of code editor".
  2. In the "Debugger" tab, uncheck "Minimize the editor in test mode".
  3. Validate.
New in version 18

Note: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "Options of code editor".
  2. In the "Debugger" tab, uncheck "Minimize the editor in test mode".
  3. Validate.

Note: Minimizing (or not) the editor during the test

During a test, the editor is minimized by default. Depending on the hardware configuration (large screen, 2 screens, ....), this minimize operation is not required.
To keep the editor opened:
  1. On the "Home" pane, in the "Environment" group, expand "Options" and select "Options of code editor".
  2. In the "Debugger" tab, uncheck "Minimize the editor in test mode".
  3. Validate.

Stopping the test of a report

Several methods can be used to stop the test:
  • 1st method: Close the preview of the report whose test is currently run. The current editor at the time the test was started is displayed.
  • 2nd method: Go back to the editor with the taskbar or with [Alt]+[Tab] and confirm the ending of the test. The current editor at the time the test was started is displayed.
  • 3rd method: Go back to the editor with the taskbar or with [Alt]+[Tab] and click Stopping the test ("End the test" option) found in the "Debugger" pane.
Notes

Directory of the files used for test

To specify the data files used when running the test of the application in the editor:
  1. Display the project description ("Project .. Project description").Display the project description: on the "Project" pane, in the "Project" group, click "Description".
  2. In the "Files" tab, select the location of test files:
    • Directory of the current configuration (option selected by default): The data files will be found in the sub-directory corresponding to the current configuration (sub-directory of EXE directory of the project).
    • Specific directory: The data files will be found in the specified directory.
    • Data directory of the application: This choice is recommended in Windows Vista. The "local" data files will be found in a directory accessible and modifiable by the application (without specific rights).

Managing passwords (analysis or data file)

No password is requested when running the test of a report linked to a password-protected data file.
The necessary passwords must be specified by programming in the "Opening" process of the report:
  • If the report is linked to one or more password-protected data files, this password must be specified in HPass.
  • A WLanguage error occurs when running the report test if the passwords are not specified in the "Opening" process of the report.
Windows Mobile

Special case for WINDEV Mobile: Opening a window in test mode in the code of the project

During the test of a report, a WLanguage error occurs if a window is opened in the initialization code of the project or in the end code of the project.
To avoid this error, InTestMode must be used to configure the window opening. For example:
IF InTestMode() = False THEN Open(WIN_MyWindow)
However, you have the ability to use the functions for opening the system information boxes (Info or Trace for example).
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment