Start vitals command
Starts collecting part or all of the real-time vitals data generated by the device until the Vitals stop command is invoked or the script ends. The collected information helps determine how efficient an application is at using resources as well as measuring the general device performance.
Application vitals: It is possible to collect application-specific vital measurements from mobile devices. Vitals will be separately collected for all of the selected services. Available application vitals:
- For Android: Memory Used, CPU Used, and CPU Kernel. CPU vitals are only supported for Android for 7 and earlier.
- For iOS (8.0 and up): Memory Used, and CPU Total.
Vitals in automation and interactive: The Vitals start function performs the same operation as the Vitals feature in the Manual Testing view. When performing manual and automation testing interactively, the following details are important:
- Starting and stopping the vitals collection during automation testing does not affect manual testing
- Stopping the vitals collection during manual testing stops the vitals collection during automation testing
- Running an automation script with vitals collection displays the vitals in the Manual Testing view
- Manual testing and automation testing produce separate CSV files
A single, multiple, or all vitals can be stopped at any point within the script.
Parameters
Name |
Type |
Possible values |
Description |
---|---|---|---|
Device ID* |
Device |
|
The device for this command. By default, this is the device under test (DUT). |
Vitals |
String |
All | Memory Used | Memory Cache| Memory Free | CPU User | CPU Kernel | CPU Total | Network Out - Data | Network In - Data | Network Out - WiFi | Network In - WiFi | Network Out - Total | Network In - Total |
The Vitals to collect, where:
|
Interval |
Number |
|
The data collection frequency, in seconds. Recommended between 10 and 30. |
Comment |
String |
Adds a comment to the script |
|
On-fail Result* |
Condition |
Ignore | Break | Continue | Abort | Catch |
The behavior when the command fails. |
* Mandatory parameter