Running the test of a Mobile application

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

This content comes from an automatic translation.

Overview
Test in the simulator
Test in the emulator
Test in native
Direct test on the device connected to the development computer
Test and debug on the Pocket PC connected to the development computer
Running a test while using a command line
Stopping the project test
Stopping the test of a project in simulator mode
Stopping the test of a project in the emulator
Stopping the test of a project on the mobile device
Remarks
Directory of data files used for test

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

Running the test of a Mobile application

Overview

The test of the entire project is used to simulate the start of the application by the user (executable, package, ...). This allows you to run the test of entire application, even if its development is not finished yet.

Summary table of available tests according to the platforms:

	Simulator (Development computer)	Emulator	Native (on the device)

Android	X	X (on PC)	X (connected device)
iOS	X	X (on MAC)
Windows Mobile	X		X (connected device) Debug possible
Universal Windows 10 App	X		X

Overview of the different types of tests
Several types of project tests are available in WINDEV Mobile:

Test in a simulator (Test on the development computer):
This test simulates a mobile device on the development computer. No connection to a mobile device is required during this test. This test allows you to use the debugger. However, this test being run on a PC and not on the real device, the application may behave differently in some ways.
Test on an emulator:
The SDK is supplied with a device emulator. The test of the application can be run in an emulator. This option does not require a real device to run the tests but it provides a more faithful execution than the "simulator" mode.
Caution: The test in the emulator is run on "Mac".
Direct test on the device connected to the development computer.
In this case, the executable corresponding to the project is created, copied onto the device and run. When running the program on the device, the device can be disconnected from the PC. The debugger is not available.
In Windows Mobile, you also have the ability ton run a test and to debug on the Mobile Device connected to the development computer. This test allows you to use the debugger even though it is run on the Mobile Device (Pocket PC).

Test in the simulator

To run the test of the current project on the development computer (in simulation mode):

Click among the quick access buttons (or press Ctrl + F9).
Validate (if necessary) the warning window for the simulator mode.
If the first project window was not defined, a window is displayed, allowing you to select the first project window.
Versions 21 and later
If the application is intended to be used on phones and tablets, two windows are displayed:
- a window used to define the first project window on the phones.
- a window used to define the first project window on the tablets.
New in version 21
If the application is intended to be used on phones and tablets, two windows are displayed:
- a window used to define the first project window on the phones.
- a window used to define the first project window on the tablets.
If the application is intended to be used on phones and tablets, two windows are displayed:
- a window used to define the first project window on the phones.
- a window used to define the first project window on the tablets.
The editor is automatically minimized and the project is run.

Remarks:

The result of some features depends on the platform used (operating system, format of character strings, ...). Differences may occur when running the test in simulation mode and when running the application test on the device corresponding to the relevant platform.
Debugging in the simulator: The application can be debugged in the simulator. This mode is used to quickly debug a new function or to check an algorithm but it presents differences of behavior. Some examples:
- path of files: the paths used are the ones of Windows.
- format of character strings.
- functions specific to the mobiles not available.

Test in the emulator

To run the test of the current project in the emulator:

Expand among the quick access buttons and select the corresponding option: "Run the project test (emulator xxx)".
The application is automatically generated.
A window allows you to select the emulator or the device onto which the application will be copied and run. This window is used to create an emulator if necessary.
Select the requested emulator and validate.
The emulator and the application start.

Test in native

Direct test on the device connected to the development computer

To run the test of the current application on the device connected to the development computer:

Expand among the quick access buttons.
Select:
- "Run the project test (mobile device)".
- "Run the application test in real".
If the application was not generated, the wizard for generating the application is automatically started.
The application is copied onto the device and it is run.

During the test, the device can be disconnected from the PC while the application is being used. However, if the application is closed, the test can be run only if the device is reconnected to the PC.

Test and debug on the Pocket PC connected to the development computer

To run the test of the current application on the Pocket PC while using the debugger of WINDEV Mobile:

Expand among the quick access buttons.
Select "Debug the project (mobile device)"
If the application was not generated, the wizard for generating the application is automatically started.
The application is copied onto the device and it is run. The debugger is available during this test. This enables you to follow the progress of the application. See Running a project step by step for more details.

Remark: No dynamic correction is available during this test.

Running a test while using a command line

To run the test of a project using a command line, all you have to do is specify this command line: Under "Project", scroll down "Test mode" and select "Test mode setting".

The different elements of the command line will be passed in parameter to the program whose test is currently run.

Reminder: These parameters can be retrieved by programming with OrderLine.

Stopping the project test

Stopping the test of a project in simulator mode

In simulator mode, several methods can be used to stop the test:

1st method: Close the application whose test is currently run (via an option used to close the application for example). WINDEV displays the editor that was used at the beginning of test.
2nd method: Close the window where the test of the Pocket PC application is run.
3rd method: Go back to the editor with the taskbar (or Alt + Tab) and confirm that the test must be stopped. WINDEV displays the editor that was used at the beginning of test.

Stopping the test of a project in the emulator

To stop the test of a project in the emulator, all you have to do is close the application in the emulator.

You also have the ability to close the emulator. However, the emulator taking quite a long time to be started, we advise you to leave it opened if several tests must be run.

Stopping the test of a project on the mobile device

During the direct test on the device, all you have to do is stop the application on the device.

Remarks

Directory of data files used for test

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

Open the project description: under the "Project" section, in the "Project" group, click on "Description".
In the "File" tab, select the location of the test files:
- Current directory: The data files will be in the project EXE subdirectory.
- Specific directory: The data files will be found in the specified directory.

Reminder: When running the test of the application, the data files used are those found on the development computer. The file system also corresponds to the Windows system for PC. To avoid any problem when actually using the application, use InTestMode to differentiate between the access to the data files in test mode and at run time. See Differences noticed between a simulation and a real execution for more details