After choosing the project, you can click Live Testing>Remote Debugging to start Remote Debugging.
Device is mainly divided into the following categories:
1. Local device: You can connect your local device to the UDT platform through the [UDT-Desktop] client tool.
2. Private cloud devices: Support the establishment of a WeTest private cloud equipment pool for you. This equipment pool is exclusive to you and your team for remote debugging and automation. If you need more information about Private Cloud, please contact us.
3. Trial devices: We provide available Trial devices for free with a 30-day trial. If you need trial devices to test, please contact us.
You can choose devices and click the start button on the right to enter the debugging page of the device.
The remote debugging page contains the remote screen of the device and various debugging tools. You can operate the device on the web at any time.
If the application to be debugged has not been uploaded, click on “Upload App” to upload it.
Enter the [application] tab, click “Upload App” to upload the file.
If the application is already in the list of uploaded applications, click the “Install” button to install the app.
When the app is installed, it supports displaying the upload speed and upload progress; it also supports reinstalling and unstalling the app.
During the installation process, you can cancel the installation by clicking the Cancel on the right.
After debugging the app, if you need to uninstall the app, you can click the uninstall button to uninstall the app from your phone.
Support for taking a screenshot and downloading all the screenshoots.
You can enable real-time logging for this device and download log files.
Support for filtering logs and setting the maximum number of lines for terminal caching.
You can filter the log levels and enter keywords to search.
Click on the Export Download button to download the log locally.
WDB(WeTest Debug Bridge) is a tool that let your local computer to connect to the remote cloud device for conveniently debugging the device locally. Please follow the instructions below to start remote debugging.
(1)Download the wdb tool,copy command to terminal and run the command to connect to the UDT iOS device.
You can use tools on Windows to debug the iOS remote device now.You can use tools on Windows to debug the remote device now.
(2)Use ./wdb devices to see the devices you have connected.
(3)After finishing your remote debugging, use ./wdb disconnect to disconnect with devices.
(1)Download the wdb tool, copy command to terminal and run the command to connect to the UDT iOS device.
(2)If the port is already in use, you can use wdb -p
(3)Use ./wdb devices to see the devices you have connected. You can use tools on MacOS
to debug the remote device now.
(4)After finishing your remote debugging, use ./wdb disconnect to disconnect with devices.
(1)Open a real device in Live Testing.
(2)Download the wdb tool,copy command to terminal and Run the command to connect to the UDT iOS device.
(3)Use ./wdb devices to see the devices you have connected. You can use tools on Linux to debug the iOS remote device now.
(4)After finishing your remote debugging, use ./wdb disconnect to disconnect with devices
You can browse mobile files here through the right interface, which allows you to perform file uploads, file downloads, folder creation, and more.
Click the icon to switch the file display style.
Select the file, click on the Download icon and choose the format you want to download.
Note: Due to limitations in the Android system, some files cannot be downloaded. Generally, files in the /sdcard directory can be downloaded.
Select the file and click on the icon to view the file information.
Click the multi-select icon to enter multi-select mode and then select multiple files to download.
Android: Due to limitations of the Android system, you can only create files or folders under the /sdcard and /data/local/tmp paths.
** iOS**: Support creating files or folders in the paths /afc, apps/bundle_id/Documents.
NOTE:
You can enter the relevant operation commands below.
After testing session, click End Debugging button.
A test record is generated for each remote commissioning of the device, including test ID, device type, device ID, device brand, model information, commissioner, commissioning time, etc.
After the test, you can click Remote Debugging>Test Results to see the debug records.