Yes, screenshots are supported and can be called through the interface.
PerfDogService is a paid module, separate from PerfDog. It is more suitable for scenarios such as automated testing, cloud testing, or customized demand customization.
Determine the process based on the package name.
If you do not save first, the data will be cleared after stopping and restarting. This depends on your needs.
After uploading, caseID will be returned.
Turn off the display of the floating box (the parameters of the StartTestAppReq interface support turning off the display of the floating box).
Save_data upload can be called again.
The same token of PerfDogService can be deployed on different machines. Consult your business classmates during the purchase process to increase the number of deployment machines.
In the PerfDogService installation file directory, there is the "Perfdog.proto" file, which can be viewed.
1. Start a script for each device, specifying the device ID and application name as parameters [Recommended and easy to implement].
2. Connect to N mobile phones, call startDeviceMonitor to monitor the devices, and open a thread to test when receiving a device.
Refer to the "Indicator Parameter Mapping Table" to add: https://perfdog.wetest.net/article_detail?id=176&issue_id=0&plat_id=2.
Possible reasons:
- FPS cannot be collected during the test.
- The test application was not started after starting the test. This could be due to the device not starting, a wrong package name, or two versions of the same app installed on the device.
Currently, specifying a port is not supported.
- After starting the application, call getAppWindowsMap to get the window list and find the window named SurfaceView.
- Fill in the window name into the subWindow field of StartTestAppReq, then call StartTestApp.
In addition to the manual, refer to perfdog.proto for the definition file of the gRPC interface and protobuf structure.