Package-level declarations
Types
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.
Test Loops are tests that can be launched by the app itself, determining when to run by listening for an intent.
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. 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" }
Encapsulates the metadata for basic sample series represented by a line chart
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.
A reference to a file.
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.
iOS app information
A Robo test for an iOS application.
A game loop test of an iOS application.
A iOS mobile test specification
A test of an iOS application that uses the XCTest framework.
One dimension of the matrix of different runs of a step.
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.
Stores rollup test status of multiple steps that were run as a group and outcome of each individual step.
Details for an outcome with a SKIPPED outcome summary.
The details about how to run the execution.
A stacktrace.
Details for an outcome with a SUCCESS outcome summary. LINT.IfChange
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 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.