Record Performance Transactions
Functional testing alone no longer suffices to deliver outstanding user experiences. To ensure optimal performance, our platform integrates performance testing, focusing on delivering the best user experience possible.
This is achieved by creating a Performance Transaction.
Description
A Performance Transaction represents a user flow. Whether you're launching an application, navigating to a new page, logging in, or completing a payment transaction, any user flow that causes a change in state can be considered a Performance Transaction.
By creating a Performance Transaction, we can capture device metrics specific to the user flow being tested.
The following metrics are captured as part of each Performance Transaction:
Metric | Description |
---|---|
Duration | Duration of the entire transaction, from start to end |
Speed Index | Computed overall score of how quickly the final content was painted |
CPU | Average and maximum values for the transaction |
Memory | Average and maximum values for the transaction |
Battery | Average and maximum values for the transaction |
Network | Total of Uploaded/Downloaded KBs during the transaction based on the Network Profile applied |
Network Calls | All the network calls made during the transaction |
To learn more about how we capture various metrics, refer to the following resources:
Getting to the Transaction Recorder
First thing you’ll need is to open a Mobile Device in a Mobile Studio session. For guidance, refer to the Getting Started with Mobile Devices section.
Within the Mobile Studio session, navigate to the Performance button.
Before starting a Performance Transaction, you can select a Network Profile to simulate specific network conditions, allowing you to validate the behavior of the application being tested.
Default Network Profile Note: The default network profile is “None”. When “None” is selected, no network traffic will be captured, and the mobile device will use the Wi-Fi network it is connected to.
You can create additional Network Profiles based on your needs. For guidance, refer to Create a new Network Profile.
If a Network Tunneling session is active, Network Traffic will not be captured.
Capturing a Performance Transaction
As soon as you start a Performance Transaction by clicking on Record, the application in the foreground will become the focus for the metrics being captured.
Once you are finished, click Stop. You’ll then be prompted to provide a name for the Performance Transaction.
A Performance Transaction is limited to a maximum duration of 5 minutes.
Automation: Performance Transactions can also be automated and embedded within your Appium scripts.
Viewing the Performance Transaction Report
Once the Performance Transaction is appropriately named, you'll have the option to view the report. In this report, you can find all the captured metrics for the transaction.
REST API: All Performance Transaction data can also be fetched via our REST API.