Test execution details
The Test execution details dataset offers vital insights into software testing, aiding teams in monitoring progress, identifying improvement areas, and assessing product quality. As a Quality Assurance Manager, it helps track test execution, assess test case effectiveness, and gauge application stability. Key scenarios include analyzing test coverage, monitoring release stability, identifying defects' root causes, optimizing resource allocation, and driving continuous improvement initiatives. This dataset helps you gain insights into business scenarios such as:
- View the trend of test executions across the test application platform
- View the test execution status by devices and the execution report details
- Understand the test execution overview at various application levels and the test device execution details
This dataset includes only active test execution records for Android and iOS platforms. It shows data from the past few months based on the configured time range. Time zone settings are applied to ensure accurate date filtering.
The following are the components of this dataset:
Attributes
| Attribute Name | Description |
|---|---|
| Application build version | The build version of the test application |
| Application platform | Name of the mobile platform |
| Application release version | The release version of the test application |
| Calendar date | Gregorian calendar date displayed in the format ‘D/M/YYYY’ |
| Calendar month | Gregorian calendar date displayed in the format 'Mon YYYY' |
| Lagging count of days | Displays the day number relative to the latest extract date and is used as a filter to retrieve past or future records |
| Lagging count of month | Displays the month number relative to the month that corresponds to the latest extract date and is used as a filter to retrieve past or future records. |
| Last refresh date | The most recent date and time when the ETL (Extract, Transform, Load) process successfully refreshed the data. This indicates how up-to-date the dataset is. |
| Project | Name of the project |
| Sys_source | Unique identifier for the source |
| Test application | Application that is being tested |
| Test device | Name of the test device |
| Test device category | Category of the test device, such as Phone or Tablet |
| Test device manufacturer | Manufacturer name of the test device, such as Apple, Samsung, Xiaomi, and so on |
| Test device model | Model number of the test device, such as iPhone 8, iPad Air, Redmi 6, and so on. |
| Test device os | Operating System of the test device, such as iOS or Android. |
| Test device screensize | Size of the test device's screen in pixels. For example: 640x1136, 1080x1920 |
| Test error classification | Error classification of a test case |
| Test execution cause | Root cause for the test execution failure |
| Test execution environment | The Continuous Testing cloud environment |
| Test execution report url | URL or path where the test execution summary report is available |
| Test execution status | Status of the test device as mentioned in the source, such as error, offline, online, unauthorized |
Metrics
| Metric Name | Description | Formula |
|---|---|---|
| % Failed test executions | Percentage of test executions that are failed, out of total test executions created. | [No of failed test executions]/[No of test executions] |
| No of Test Executions | Total count of test executions | Count(Test number) |
| No of Failed Test Executions | Count of test executions that have failed | Count (Failed test executions) |
| No of Passed Test Executions | Count of test executions that have passed | Count (Passed test executions) |