google_api_tool_results v0.20.0 API Reference
Modules
Handle Tesla connections for GoogleApi.ToolResults.V1.
Additional details for an ANR crash.
A suggestion to use deep links for a Robo run.
A warning that Robo encountered a screen that was mostly blank; this may indicate a problem with the app.
Crash dialog was detected during the test execution
Additional details about encountered login screens.
Additional details about encountered screens with elements that are not Android UI widgets.
Failed to install the APK.
Additional details for a fatal exception.
Additional details of in-app purchases encountered during the crawl.
A warning that Robo did not crawl potentially important parts of the app.
Additional details for an iOS app crash.
Failed to find the launcher activity of an app.
Additional details for a native crash.
A non-sdk API and examples of it being called along with other metadata See https://developer.android.com/distribute/best-practices/develop/restrictions-non-sdk-interfaces
Non-SDK API insights (to address debugging solutions).
Additional details for a non-sdk API usage violation.
Contains a summary and examples of non-sdk API usage violations.
A warning that Robo encountered a screen that has overlapping clickable elements; this may indicate a potential UI issue.
This insight indicates that the hidden API usage originates from a Google-provided library. Users need not take any action.
A notification that Robo signed in with Google.
A notification that Robo performed some monkey actions.
Execution stats for a user-provided Robo script.
A stacktrace.
User provided intent failed to resolve to an activity.
A warning that the screen hierarchy is deeper than the recommended threshold.
Default unspecified warning.
Additional details of an unused robodirective.
This insight is a recommendation to upgrade a given library to the specified version, in order to avoid dependencies on non-SDK APIs.
Additional details of a used Robo directive.
Additional details of a used Robo directive with an ignore action. Note: This is a different scenario than unused directive.
API calls for all endpoints tagged Projects
.
Handle Tesla connections for GoogleApi.ToolResults.V1beta3.
Android app information.
A test of an Android application that can control an Android component independently of its normal lifecycle.
A test of an android application that explores the application on a virtual or physical Android device, finding culprits and crashes as it goes.
An Android mobile test specification.
Any
contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message.
Attributes
fullyDrawnTime
(type:GoogleApi.ToolResults.V1beta3.Model.Duration.t
, default:nil
) - Optional. The time from app start to reaching the developer-reported "fully drawn" time. This is only stored if the app includes a call to Activity.reportFullyDrawn(). See https://developer.android.com/topic/performance/launch-time.html#time-fullinitialDisplayTime
(type:GoogleApi.ToolResults.V1beta3.Model.Duration.t
, default:nil
) - The time from app start to the first displayed activity being drawn, as reported in Logcat. See https://developer.android.com/topic/performance/launch-time.html#time-initial
Encapsulates the metadata for basic sample series represented by a line chart
The request must provide up to a maximum of 5000 samples to be created; a larger sample size will cause an INVALID_ARGUMENT error
A Duration represents a signed, fixed-length span of time represented as a count of seconds and fractions of seconds at nanosecond resolution. It is independent of any calendar and concepts like "day" or "month". It is related to Timestamp in that the difference between two Timestamp values is a Duration and it can be added or subtracted from a Timestamp. Range is approximately +-10,000 years.
An Environment represents the set of test runs (Steps) from the parent Execution that are configured with the same set of dimensions (Model, Version, Locale, and Orientation). Multiple such runs occur particularly because of features like sharding (splitting up a test suite to run in parallel across devices) and reruns (running a test multiple times to check for different outcomes).
An Execution represents a collection of Steps. For instance, it could represent: - a mobile test executed across a range of device configurations - a jenkins job with a build step followed by a test step
Details for an outcome with a FAILURE outcome summary.
A reference to a file.
Graphics statistics for the App. The information is collected from 'adb shell dumpsys graphicsstats'. For more info see: https://developer.android.com/training/testing/performance.html Statistics will only be present for API 23+.
A History represents a sorted list of Executions ordered by the start_timestamp_millis field (descending). It can be used to group all the Executions of a continuous build.
An image, with a link to the main image and a thumbnail.
Details for an outcome with an INCONCLUSIVE outcome summary.
Step Id and outcome of each individual step that was run as a group with other steps with the same configuration.
Response message for EnvironmentService.ListEnvironments.
Response message for HistoryService.List
Attributes
nextPageToken
(type:String.t
, default:nil
) - Optional, returned if result size exceeds the page size specified in the request (or the default page size, 500, if unspecified). It indicates the last sample timestamp to be used as page_token in subsequent requestperfSamples
(type:list(GoogleApi.ToolResults.V1beta3.Model.PerfSample.t)
, default:nil
) -
A response containing the thumbnails in a step.
Response message for StepService.List.
Response message for StepService.ListTestCases.
Merged test result for environment.
Details when multiple steps are run with the same configuration as a group.
Interprets a result so that humans and machines can act on it.
Encapsulates performance environment info
A summary of perf metrics collected and performance environment info
Resource representing a single performance measure or data point
Resource representing a collection of performance samples (or data points)
Stores rollup test status of multiple steps that were run as a group and outcome of each individual step.
Per-project settings for the Tool Results service.
Request message for StepService.PublishXunitXmlFiles.
The storage for test results.
Attributes
fileReference
(type:String.t
, default:nil
) - File reference of the png file. Required.locale
(type:String.t
, default:nil
) - Locale of the device that the screenshot was taken on. Required.model
(type:String.t
, default:nil
) - Model of the device that the screenshot was taken on. Required.version
(type:String.t
, default:nil
) - OS version of the device that the screenshot was taken on. Required.
Attributes
activity
(type:String.t
, default:nil
) - A string that describes the activity of every screen in the cluster.clusterId
(type:String.t
, default:nil
) - A unique identifier for the cluster.keyScreen
(type:GoogleApi.ToolResults.V1beta3.Model.Screen.t
, default:nil
) - A singular screen that represents the cluster as a whole. This screen will act as the "cover" of the entire cluster. When users look at the clusters, only the key screen from each cluster will be shown. Which screen is the key screen is determined by the ClusteringAlgorithmscreens
(type:list(GoogleApi.ToolResults.V1beta3.Model.Screen.t)
, default:nil
) - Full list of screens.
Result summary for a shard in an environment.
Details for an outcome with a SKIPPED outcome summary.
The details about how to run the execution.
A stacktrace.
The Status
type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status
message contains three pieces of data: error code, error message, and error details.
A Step represents a single operation performed as part of Execution. A step can be used to represent the execution of a tool ( for example a test runner execution or an execution of a compiler).
Details for an outcome with a SUCCESS outcome summary. LINT.IfChange
A reference to a test case.
A step that represents running tests.
An issue detected occurring during a test execution.
A summary of a test suite result either parsed from XML or uploaded directly by a user.
Testing timing break down to know phases.
A single thumbnail, with its size and format.
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
An execution of an arbitrary tool. It could be a test runner or a tool copying artifacts or deploying code.
Generic tool step to be used for binaries we do not explicitly support. For example: running cp to copy artifacts from one location to another.
Exit code from a tool execution.
A reference to a ToolExecution output file.