API to publish and access results from developer tools.

Android app information.

A test of an Android application that can control an Android component independently of its normal lifecycle. See for more information on types of Android tests.

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.

Test Loops are tests that can be launched by the app itself, determining when to run by listening for an intent.

Additional details for an ANR crash.

Any contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := ptypes.MarshalAny(foo) ... foo := &pb.Foo{} if err := ptypes.UnmarshalAny(any, foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". # JSON The JSON representation of an Any value uses the regular representation of the deserialized, embedded message, with an additional field @type which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": , "lastName": } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field value which holds the custom JSON in addition to the @type field. Example (for message google.protobuf.Duration): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" }

There was an issue with the assets in this test.

A suggestion to use deep links for a Robo run.

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 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

Defines the root interface for all clients that generate credentials for calling Google APIs. All clients should implement this interface.

A notification that Robo detected a splash screen provided by app (vs. Android OS splash screen).

A warning that device ran out of memory

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.

Additional details about encountered login screens.

Additional details about encountered screens with elements that are not Android UI widgets.

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 The maximum size of an execution message is 1 MiB. An Execution can be updated until its state is set to COMPLETE at which point it becomes immutable.

Failed to install the App.

Details for an outcome with a FAILURE outcome summary.

Additional details for a fatal exception.

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. Note that the ordering only operates on one-dimension. If a repository has multiple branches, it means that multiple histories will need to be used in order to order Executions per branch.

An image, with a link to the main image and a thumbnail.

Additional details of in-app purchases encountered during the crawl.

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.

A warning that Robo did not crawl potentially important parts of the app.

Additional details for an iOS app crash.

iOS app information

A Robo test for an iOS application.

A iOS mobile test specification

A game loop test of an iOS application.

A test of an iOS application that uses the XCTest framework.

Failed to find the launcher activity of an app.

Response message for EnvironmentService.ListEnvironments.

Response message for HistoryService.List

Response message for AccessibilityService.ListStepAccessibilityClusters.

Response message for StepService.List.

A response containing the thumbnails in a step.

Response message for StepService.ListTestCases.

A warning that there were issues in logcat collection.

One dimension of the matrix of different runs of a step.

Merged test result for environment. If the environment has only one step (no reruns or shards), then the merged result is the same as the step result. If the environment has multiple shards and/or reruns, then the results of shards and reruns that belong to the same environment are merged into one environment result.

Details when multiple steps are run with the same configuration as a group.

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.

Interprets a result so that humans and machines can act on it.

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.

Encapsulates performance environment info

A summary of perf metrics collected and performance environment info

A notification that Robo signed in with Google.

A notification that Robo performed some monkey actions.

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.

Additional options for ToolResults#projectsHistoriesCreate.

Additional options for ToolResults#projectsHistoriesExecutionsCreate.

Additional options for ToolResults#projectsHistoriesExecutionsEnvironmentsList.

Additional options for ToolResults#projectsHistoriesExecutionsList.

Additional options for ToolResults#projectsHistoriesExecutionsPatch.

Additional options for ToolResults#projectsHistoriesExecutionsStepsAccessibilityClusters.

Additional options for ToolResults#projectsHistoriesExecutionsStepsCreate.

Additional options for ToolResults#projectsHistoriesExecutionsStepsList.

Additional options for ToolResults#projectsHistoriesExecutionsStepsPatch.

Additional options for ToolResults#projectsHistoriesExecutionsStepsPerfSampleSeriesList.

Additional options for ToolResults#projectsHistoriesExecutionsStepsPerfSampleSeriesSamplesList.

Additional options for ToolResults#projectsHistoriesExecutionsStepsTestCasesList.

Additional options for ToolResults#projectsHistoriesExecutionsStepsThumbnailsList.

Additional options for ToolResults#projectsHistoriesList.

Request message for StepService.PublishXunitXmlFiles.

A rectangular region.

The storage for test results.

Execution stats for a user-provided Robo script.

IMPORTANT: It is unsafe to accept this message from an untrusted source, since it's trivial for an attacker to forge serialized messages that don't fulfill the type's safety contract -- for example, it could contain attacker controlled script. A system which receives a SafeHtmlProto implicitly trusts the producer of the SafeHtmlProto. So, it's generally safe to return this message in RPC responses, but generally unsafe to accept it in RPC requests.

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.

User provided intent failed to resolve to an activity.

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. You can find out more about this error model and how to work with it in the API Design Guide.

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). Steps can overlap (for instance two steps might have the same start time if some operations are done in parallel). Here is an example, let's consider that we have a continuous build is executing a test runner for each iteration. The workflow would look like:

• user creates a Execution with id 1 - user creates a TestExecutionStep with id 100 for Execution 1 - user update TestExecutionStep with id 100 to add a raw xml log + the service parses the xml logs and returns a TestExecutionStep with updated TestResult(s). - user update the status of TestExecutionStep with id 100 to COMPLETE A Step can be updated until its state is set to COMPLETE at which points it becomes immutable.

Lightweight summary of a step within this execution.

Details for an outcome with a SUCCESS outcome summary. LINT.IfChange

A set of similar suggestions that we suspect are closely related. This proto and most of the nested protos are branched from foxandcrown.prelaunchreport.service.SuggestionClusterProto, replacing PLR's dependencies with FTL's.

A reference to a test case. Test case references are canonically ordered lexicographically by these three factors: * First, by test_suite_name. * Second, by class_name. * Third, by name.

A step that represents running tests. It accepts ant-junit xml files which will be parsed into structured test results by the service. Xml file paths are updated in order to append more files, however they can't be deleted. Users can also add test results manually by using the test_result field.

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. Note: the API related comments are for StepService only. This message is also being used in ExecutionService in a read only mode for the corresponding step.

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. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.

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.

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.