Running the test of a project: setting

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Overview
Configuring the test mode
Command line
Directory of the files used for test
Runtime directory
Vista manifest
Other user account
Debugging options

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

Running the test of a project: setting

Overview

The test of entire project is used to simulate the application start by the executable. This allows you to run the test of entire application, even if its development is not finished yet. As soon as a problem occurs in the execution of the project, the debugger can be started to identify and fix the problem.

Different parameters are used to:

Run the test of a project by specifying a command line.
Run the test of a project by specifying a specific runtime directory.
Run the test of a project with a manifest (in Windows Vista only).
Run the test of a project by using the rights granted to another user. This setting is used to check the operating mode of the application by simulating the UAC mechanism in Windows Vista.

Note: The test of a project can be run regardless of the current element in the editor.

Configuring the test mode

Command line

To run the test of a project using a command line, this command line must be specified via "Project .. Test mode .. Configure the test mode" (Ctrl + Shift + F9).To run the test of a project using a command line, all you have to do is specify this command line:

On the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Configure the test mode" (or press the Shift + Ctrl + F9).
Type the command line.
- Versions 20 and later
  The custom command line corresponds to custom parameters used to run the project test.
  New in version 20
  The custom command line corresponds to custom parameters used to run the project test.
  The custom command line corresponds to custom parameters used to run the project test.
- Versions 20 and later
  The common command line corresponds to common parameters used to run the project test. These parameters are saved in the project and they are taken into account when the project is shared via the SCM.
  New in version 20
  The common command line corresponds to common parameters used to run the project test. These parameters are saved in the project and they are taken into account when the project is shared via the SCM.
  The common command line corresponds to common parameters used to run the project test. These parameters are saved in the project and they are taken into account when the project is shared via the SCM.
The command line used during the test is displayed (concatenation of common and custom command lines).

The different elements of the command line will be passed in parameter to the current program.

Reminder: these parameters can be retrieved by programming with CommandLine.

Directory of the files used for test

To configure the data files used when running the application test in the editor:

Display the project description ("Project .. Project description").Display the project description: on the "Project" pane, in the "Project" group, click "Description".
In the "Files" tab, select the location of test files:
- Directory of the current configuration or current directory: The data files used will be found in the sub-directory corresponding to the project configuration (sub-directory of EXE directory of project).
- Specific directory: The data files will be found in the specified directory.
- Directory of the application data (recommended when using the application in Windows XP, Windows Vista and later). This directory is different if the data is common to all the application users or if the data is specific to each user.

Note: User groupware
If your application is using the user groupware, you must configure the location of the data files found in the user groupware. To perform this setting:

Display the description window of User Groupware ("Workshop .. Configure the user groupware"). Display the description window of the User Groupware: on the "Project" pane, in the "Project" group, click "User groupware".
Display the "Files" tab.

See Data files of user groupware for more details.See User groupware: Options and setting for more details.

Runtime directory

WINDEV allows you to run the project test in a directory other than the "EXE" directory of the project. Therefore, the test is run in conditions close to the ones found on the end-user computers.

To modify the runtime directory of the application:

Select "Project .. Test mode .. Configure the test mode".On the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Configure the test mode".
In the window that is displayed, expand "Advanced modes (Windows Vista, UAC, ...)".
In the "Runtime directory" tab, check "Start the test mode in the actual runtime directory: ".
Select the requested runtime directory.
The data files that will be taken into account are the data files found in the directories specified:
- in the project description.
- in the description of the user groupware if the user groupware is used by the application.
Click the "Copy the files" button. For each data file, you can choose the directory into which this file must be copied:
- a directory proposed by default:
  - <RuntimeDir>: Standard runtime directory of the application. This directory is identical to the one chosen in the "Runtime directory" tab.
  - <DirDataUser>: Standard directory of the application data for a specific user. In Windows XP/Vista, this directory has the following format: "C:\Documents and Settings\<User>\Application Data\<Company Name>\<Application Name>".
  - <DirCommonData>: Standard directory of application data for all users of the same computer. In Windows XP/Vista, this directory has the following format: "C:\Documents and Settings\All Users\Application Data\<Company Name>\<Application Name>".
  - <GlobalDirUser>: Standard directory of the data shared by several applications for a specific user. In Windows XP/Vista, this directory has the following format: "C:\Documents and Settings\<User>\Application Data".
  - <GlobalDirCommon>: Standard directory of data shared by several applications for all users of the same computer. In Windows XP/Vista, this directory has the following format: "C:\Documents and Settings\All Users\Application Data".
- in a directory selected via the picker ([...] option).

Vista manifest

If Windows Vista (or later) is your operating system, WINDEV allows you to run the test of your application by using a manifest. This manifest can be included in the executable of your project when creating the executable.

Using a manifest allows you to specify the level of rights required to run the application.

The available manifests are as follows:

No manifest
No privileges
Maximum user privileges
Administrator privileges
Versions 21 and later
Like in generation. This option allows you to automatically re-use the manifest characteristics specified during the last generation of application.
New in version 21
Like in generation. This option allows you to automatically re-use the manifest characteristics specified during the last generation of application.
Like in generation. This option allows you to automatically re-use the manifest characteristics specified during the last generation of application.

See Choosing a manifest for Vista for more details.

Other user account

WINDEV allows you to run the test of the project in a directory by using a user account different from the current one. This allows you to run the test of the project by using rights other than the rights granted to the user currently connected.

Indeed, in most cases, you are the administrator of your computer when developing an application. In most cases, the users of your applications are standard users. This operating mode is even truer in Windows Vista.

WINDEV allows you to run the test of your applications as a standard user: you can easily identify the problems of your applications caused by the rights and correct them if necessary.

Note: We advise you to combine this option with:

the use of a runtime directory. For Windows Vista, the runtime directory and the data directory must correspond to the Vista standards.
the use of a manifest (if your development computer runs on XP).

Caution: The management of rights is taken into account for the disks that use a NTFS file system. For the FAT32 file systems, the management of rights is not taken into account.

To run the tests by using another user account:

Create (if necessary) one or more users on your computer. New users can be created from the control panel of Windows ("User accounts").
In the "Other user account" tab, specify the characteristics of the user: Name, Password, Domain.
The next test of the application will be run with this user.

Note: You cannot use an Administrator manifest with a local user who belongs to the administrator group.

Versions 21 and later

Debugging options

WINDEV allows you to configure the debugging options specific to the test mode.

You can:

ignore the timers: This option is used to disable the timers during the debugging.
systematically stop on the unchecked exceptions, errors or assertions. In this case, in debugging mode:
- the error window is not displayed,
- the debugger is directly positioned on the corresponding code line.

These options are also available in the "Debugger" pane of the ribbon, during the test mode.

New in version 21

Debugging options

WINDEV allows you to configure the debugging options specific to the test mode.

You can:

ignore the timers: This option is used to disable the timers during the debugging.
systematically stop on the unchecked exceptions, errors or assertions. In this case, in debugging mode:
- the error window is not displayed,
- the debugger is directly positioned on the corresponding code line.

These options are also available in the "Debugger" pane of the ribbon, during the test mode.

Debugging options

WINDEV allows you to configure the debugging options specific to the test mode.

You can:

ignore the timers: This option is used to disable the timers during the debugging.
systematically stop on the unchecked exceptions, errors or assertions. In this case, in debugging mode:
- the error window is not displayed,
- the debugger is directly positioned on the corresponding code line.

These options are also available in the "Debugger" pane of the ribbon, during the test mode.