|
|
|
|
|
- Overview
- Test in the simulator
- Test in the emulator
- Test in native
- Direct test on the device connected to the development computer
- 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 the data files used for testing
Testing a Mobile application
To run the test of the current project on the development computer (in simulation mode): - Click
in the quick access buttons (or press Ctrl + F9). - If the first project window was not defined, a window is displayed, allowing you to select the first project window.
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.
- Validate (if necessary) the warning window for the simulator mode.
- The editor is automatically minimized and the project is run.
Remarks: - The result of certain functions depends on the platform used (operating system, string format, etc.). 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: You can debug your application in the simulator.. This mode is used to quickly debug a new function or to check an algorithm but it presents differences of behavior. For example:
- file paths: the paths used are those of Windows.
- format of character strings.
- functions specific to the mobiles not available.
Test mode options: To specify the options to be used in test mode: - On the "Project" tab, in the "Test mode" group, expand "Test mode" and select "Configure test mode".
- Specify:
- the command line to pass to the application during the test: enter the command line you want (personal or common to all users).
New in version 2025the vault management mode during the test. For more details, see Secret string vault. Note: This feature is only available from version 2025 Update 1. For more details, see Test mode settings. Testing a Widget iOS 14 application: Widget iOS 14 windows can be tested directly in the WINDEV Mobile simulator.. The characteristics of Widget windows are taken into account.
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 under test (using an option to close the application, for example). WINDEV or WINDEV Mobile displays the editor that was open when the test was started.
- 2nd method: Close the application test window.
- 3rd method: Return to the editor using the taskbar or Alt + Tab and confirm that you want to stop the test.. WINDEV or WINDEV Mobile displays the editor that was open when the test was started.
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. Directory of the data files used for testing To configure the data files used when running the site test in the editor: - Open the project description window. To do so, go to the "Project" tab, "Project" group, and select "Description".
- In the "Data files" tab, select the location of the test files:
- Current directory: Data files will be located in the project's EXE subdirectory.
- Specified directory: the data files will be located in the specified directory.
Reminder: When testing the application, the data files used are those on the development workstation.. The file system also corresponds to the Windows system for PC. To avoid any problems when the application is used in a real-case scenario, use InTestMode to differentiate between the access to the data files in test mode and at runtime.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|