metadata

type Attribute struct {

	// Opaque name for this attribute.
	//
	// Value MUST be valid resource names per https://aip.dev/122.
	//
	// MUST NOT be interpreted by Test Lab Environments.
	Name string `protobuf:"bytes,1,opt,name=name,proto3" json:"name,omitempty"`
	// contains filtered or unexported fields
}

type Contact struct {

	// Types that are assignable to Type:
	//	*Contact_Email
	//	*Contact_MdbGroup
	Type isContact_Type `protobuf_oneof:"type"`
	// contains filtered or unexported fields
}

type Contact_Email struct {
	// e.g.: user@google.com
	Email string `protobuf:"bytes,1,opt,name=email,proto3,oneof"`
}

type Contact_MdbGroup struct {
	// e.g.: team-name (not mdb/team-name)
	MdbGroup string `protobuf:"bytes,2,opt,name=mdb_group,json=mdbGroup,proto3,oneof"`
}

type DUTCondition struct {
	Expression string `protobuf:"bytes,1,opt,name=expression,proto3" json:"expression,omitempty"`
	// contains filtered or unexported fields
}

type DUTCondition_Scope struct {
	Setup            *v1.DeviceUnderTest   `protobuf:"bytes,1,opt,name=setup,proto3" json:"setup,omitempty"`
	HardwareTopology *api.HardwareTopology `protobuf:"bytes,2,opt,name=hardware_topology,json=hardwareTopology,proto3" json:"hardware_topology,omitempty"`
	HardwareFeatures *api.HardwareFeatures `protobuf:"bytes,3,opt,name=hardware_features,json=hardwareFeatures,proto3" json:"hardware_features,omitempty"`
	// contains filtered or unexported fields
}

type DUTConfigConstraint struct {

	// A Common Expression Language (CEL) expression to specify constraints on a
	// Device Under Test's Chrome OS configuration payload. `expression` MUST
	// evaluate to a boolean value in the evaluation context described below.
	//
	// Test Lab Environments may optionally support scheduling test requests on
	// Devices Under Test that satisfy some constraints on their Chrome OS
	// configuration.
	// When supported, the Test Lab Environment MUST effectively evaluate
	// `expression` with the following declarations in scope for each available
	// Device Under Test and ensure that the test is scheduled on a Device Under
	// Test for which `expression` evaluates to true.
	//
	// - Constant: `dut` of type DUTConfigConstraint.DUT defined below, set to the
	//   Chrome OS configuration payload of a particular Device Under Test.
	// - Types: Protobuf messages from `chromiumos.config.api.*`
	//   - Additionally available with the short-hand `api.*`
	//
	// ## Examples
	//
	// Typical examples of expressions are:
	//
	// - Must run on a device with a given screen size:
	//     dut.hardware_features.screen.milliinch.value == 14000
	// - Must run on a device with LTE support:
	//     dut.hardware_features.lte == api.HardwareFeatures.Present.PRESENT
	//     - or equivalently,
	//       (dut.hardware_features.lte ==
	//        chromiumos.config.api.HardwareFeatures.Present.PRESENT)
	// - Must not run on a device with a specific form factor:
	//     (dut.hardware_features.form_factor.form_factor !=
	//      api.HardwareFeatures.FormFactor.CLAMSHELL)
	//
	// ## CEL support
	//
	// The full CEL spec can be found at https://github.com/google/cel-spec.
	//
	// Current support for `expression` evaluation is very restricted due to
	// limitations in the scheduling infrastructure used by Test Platform.
	//
	// As this API matures, features will be added to the scheduling
	// infrastructure of Test Platform and restrictions here will be lifted based
	// on requirements collected from test authors. See milestones in
	// go/cros-f20-plan for expected feature iterations. Test Lab Environments
	// SHOULD validate the expression and reject use of unsupported features.
	//
	// TODO(crbug.com/1051689) Add reference to the metadata validator package.
	//
	// ### Syntax
	//
	// See full syntax definition at
	// https://github.com/google/cel-spec/blob/master/doc/langdef.md#syntax
	//
	// CEL standard syntax allows expressions that evaluate to errors (e.g.,
	// syntax allows negation of lists, which has no semantics in CEL).
	// Thus, this spec does not attempt to restrict the syntax, but specifies what
	// operations are unsupported to aid metadata producers. Ultimately, the
	// reference metadata validator is the authority on what expressions are
	// allowed.
	//
	// Unsupported standard CEL semantics:
	//   - Binary arithmetic operations
	//     e.g.: +, *, /, % ...
	//   - Relational Operators beyond (in)equality are not supported.
	//     e.g.: (>, <, >=, <= ...)
	//   - Logical OR in expressions is not supported.
	//     e.g.: (a || b), !(a && b) ...
	//
	// ### Macros
	//
	// See full macro definition at
	// https://github.com/google/cel-spec/blob/master/doc/langdef.md#macros
	//
	// Supported macros: has(), e.all()
	// Unsupported macros: e.exists(), e.exists_one(), e.map(), e.filter()
	//
	// ### Standard functions
	//
	// See full list of standard definitions at
	// https://github.com/google/cel-spec/blob/master/doc/langdef.md#standard-definitions
	//
	// Most standard functions are not supported.
	//
	// - Supported operators: !_, -_, _!=_, _&&_, _=_, _[_]
	//   - All other operators are not supported.
	// - All other standard functions are not supported. In particular:
	//   - size() is not supported.
	//   - string functions like endsWith() and contains() are not supported.
	//   - type conversions like int() and string() are not supported.
	//   - reflection with type(), null_type() and dyn() is not supported.
	Expression string `protobuf:"bytes,1,opt,name=expression,proto3" json:"expression,omitempty"`
	// contains filtered or unexported fields
}

type DUTConfigConstraint_DUT struct {
	HardwareFeatures *api.HardwareFeatures `protobuf:"bytes,1,opt,name=hardware_features,json=hardwareFeatures,proto3" json:"hardware_features,omitempty"`
	// contains filtered or unexported fields
}

type DUTConstraint struct {

	// Conditions on the Chrome OS configuration payload.
	Config *DUTConfigConstraint `protobuf:"bytes,1,opt,name=config,proto3" json:"config,omitempty"`
	// Conditions on device setup.
	Setup *DUTSetupConstraint `protobuf:"bytes,2,opt,name=setup,proto3" json:"setup,omitempty"`
	// contains filtered or unexported fields
}

type DUTSetupConstraint struct {

	// A Common Expression Language (CEL) expression to specify constraints on a
	// Device Under Test setup. `expression` MUST evaluate to a boolean value in
	// the evaluation context described below.
	//
	// Test Lab Environments may optionally support scheduling test requests on
	// Devices Under Test that satisfy some constraints on how they are setup.
	// When supported, the Test Lab Environment MUST effectively evaluate
	// `expression` with the following declarations in scope for each available
	// Device Under Test and ensure that the test is scheduled on a Device Under
	// Test for which `expression` evaluates to true.
	//
	// - Constant: `dut` of type DUTSetupConstraint.DUT defined below, set to the
	//   setup configuration payload of a particular Device Under Test.
	// - Type: Protobuf messages `chromiumos.config.api.test.dut.v1.*`, e.g.
	//   `chromiumos.config.api.test.dut.v1.DeviceUnderTest`
	//   - Additionally available with short-hands `DeviceUnderTest` etc.
	//
	// ## Examples
	//
	// Typical examples of expressions are:
	//
	// - Must run on a DUT with servo present:
	//     dut.setup.peripheral.servo.present
	// - Must run on a DUT which is in a camera box with a front facing camera:
	//     dut.setup.peripheral.camerabox.facing == Camerabox.Facing.FRONT
	//   - Or, equivalently:
	//       (dut.setup.peripheral.camerabox.facing ==
	//        chromiumos.config.api.test.dut.v1.Camerabox.Facing.FRONT)
	//
	// ## CEL support
	//
	// The full CEL spec can be found at https://github.com/google/cel-spec.
	//
	// Current support for `expression` evaluation is very restricted due to
	// limitations in the scheduling infrastructure used by Test Platform.
	//
	// As this API matures, features will be added to the scheduling
	// infrastructure of Test Platform and restrictions here will be lifted based
	// on requirements collected from test authors. See milestones in
	// go/cros-f20-plan for expected feature iterations. Test Lab Environments
	// SHOULD validate the expression and reject use of unsupported features.
	//
	// TODO(crbug.com/1051689) Add reference to the metadata validator package.
	//
	// ### Syntax
	//
	// See full syntax definition at
	// https://github.com/google/cel-spec/blob/master/doc/langdef.md#syntax
	//
	// CEL standard syntax allows expressions that evaluate to errors (e.g.,
	// syntax allows negation of lists, which has no semantics in CEL).
	// Thus, this spec does not attempt to restrict the syntax, but specifies what
	// operations are unsupported to aid metadata producers. Ultimately, the
	// reference metadata validator is the authority on what expressions are
	// allowed.
	//
	// Unsupported standard CEL semantics:
	//   - Binary arithmetic operations
	//     e.g.: +, *, /, % ...
	//   - Relational Operators beyond (in)equality are not supported.
	//     e.g.: (>, <, >=, <= ...)
	//   - Logical OR in expressions is not supported.
	//     e.g.: (a || b), !(a && b) ...
	//
	// ### Macros
	//
	// See full macro definition at
	// https://github.com/google/cel-spec/blob/master/doc/langdef.md#macros
	//
	// Supported macros: has(), e.all()
	// Unsupported macros: e.exists(), e.exists_one(), e.map(), e.filter()
	//
	// ### Standard functions
	//
	// See full list of standard definitions at
	// https://github.com/google/cel-spec/blob/master/doc/langdef.md#standard-definitions
	//
	// Most standard functions are not supported.
	//
	// - Supported operators: !_, -_, _!=_, _&&_, _=_, _[_]
	//   - All other operators are not supported.
	// - All other standard functions are not supported. In particular:
	//   - size() is not supported.
	//   - string functions like endsWith() and contains() are not supported.
	//   - type conversions like int() and string() are not supported.
	//   - reflection with type(), null_type() and dyn() is not supported.
	Expression string `protobuf:"bytes,1,opt,name=expression,proto3" json:"expression,omitempty"`
	// contains filtered or unexported fields
}

type DUTSetupConstraint_DUT struct {

	// Peripherals information about the lab deployment of the device
	Setup *v1.DeviceUnderTest `protobuf:"bytes,1,opt,name=setup,proto3" json:"setup,omitempty"`
	// contains filtered or unexported fields
}

type DockerImage struct {

	// The Docker image digest is a content-addressable identifier for an image.
	//
	// The source of the Remote Test Driver images (e.g., a Docker registry, or
	// a local Docker server) is specified in the Test Lab Environment request.
	// The test metadata only contains the digest of the image to use.
	//
	// TLEs SHOULD verify the downloaded image against the digest.
	//
	// The digest MUST be set in metadata payload used by the Test Lab
	// Environments. There is only one case where the digest may be elided:
	//
	// It may be useful for Remote Test Driver images to contain a
	// copy of the metadata payload (e.g. to map from Test name to some Remote
	// Test Driver-internal execution behaviour). This creates a chicken-and-egg
	// problem: Changing the image name changes the image content, thereby
	// changing the image hash again. In such cases, digest may be elided in the
	// metadata payload inside the Remote Test Driver image.
	Digest string `protobuf:"bytes,1,opt,name=digest,proto3" json:"digest,omitempty"`
	// contains filtered or unexported fields
}

type Informational struct {

	// Contacts for ownership / flakiness notification etc.
	Authors []*Contact `protobuf:"bytes,1,rep,name=authors,proto3" json:"authors,omitempty"`
	// Machine readable test-specific information.
	//
	// Remote Test Drivers SHOULD include detailed information to aid analytics.
	// For example, test authors may minimize code duplication by writing
	// paramterized tests. Thus, multiple test metadata may refer to the
	// same test implementation with different arguments. It is useful to include
	// this information as details. An example for Tauto:
	//   {
	//      "test_project": "chromiumos/third_party/autotest",
	//      "control_file": "site_tests/dummy_Pass/control.stress",
	//      "args": {
	//        "run_count": 35
	//      }
	//   }
	//
	// This field MUST NOT be interpreted by the Test Lab Environments, but Remote
	// Test Drivers can enrich analytics by using uniform stable schema for
	// details across all their tests.
	Details *structpb.Struct `protobuf:"bytes,2,opt,name=details,proto3" json:"details,omitempty"`
	// contains filtered or unexported fields
}

type RemoteTestDriver struct {

	// Globally unique name for a Remote Test Driver package.
	//
	//
	// MUST be a valid resource per https://aip.dev/122.
	//
	// Pattern: remoteTestDrivers/{remoteTestDriver}
	//
	// The two most commonly used Remote Test Drivers are named
	// - remoteTestDrivers/tauto
	// - remoteTestDrivers/tast
	// and contain the common public tests written in the Tauto and Tast framework
	// respectively.
	Name string `protobuf:"bytes,1,opt,name=name,proto3" json:"name,omitempty"`
	// A Docker image containing all the required dependencies and other build
	// artifacts required for test invocations.
	//
	// Test Lab Environments SHOULD fail with an error indicating that the request
	// was invalid if the image fails to be found for a test invocation.
	//
	// See go/cros-f20-rtd-design for details about how the docker image should
	// be prepared.
	DockerImage *DockerImage `protobuf:"bytes,5,opt,name=docker_image,json=dockerImage,proto3" json:"docker_image,omitempty"`
	// Command to invoke the Remote Test Driver inside `image`.
	//
	// Remote Test Servers MUST run `command` as
	//   $ ${command} -input ${input}
	// where ${command} and ${input} are absolute paths inside the container.
	//
	// Remote Test Servers MUST populate `input` with a binaryproto file
	// representing a test.invocation.Invocation message.
	Command string `protobuf:"bytes,3,opt,name=command,proto3" json:"command,omitempty"`
	// Metadata for the smallest schedulable test units.
	Tests []*Test `protobuf:"bytes,4,rep,name=tests,proto3" json:"tests,omitempty"`
	// contains filtered or unexported fields
}

type Specification struct {

	// A set of Remote Test Driver packages.
	//
	// In practice, a complete specification of all known Remote Test Drivers may
	// consist of multiple Specification instances. In that case the test names
	// MUST be unique across different Specification instances.
	//
	// Unlike tests, a RemoteTestDriver (identified by its name) may be specified
	// multiple times, in a single Specification or across different Specification
	// instances. In that case, all fields except the list of tests MUST be
	// identical across these RemoteTestDriver instances. The list of tests across
	// these instances will be concatenated together.
	RemoteTestDrivers []*RemoteTestDriver `protobuf:"bytes,1,rep,name=remote_test_drivers,json=remoteTestDrivers,proto3" json:"remote_test_drivers,omitempty"`
	// contains filtered or unexported fields
}

type Test struct {

	// Globally unique name for this test.
	//
	// MUST be a valid resource per https://aip.dev/122.
	//
	// Pattern: remoteTestDrivers/{remoteTestDriver}/tests/{test}
	//   where {remoteTestDriver} is the Remote Test Driver package that
	//   contains this test.
	Name string `protobuf:"bytes,1,opt,name=name,proto3" json:"name,omitempty"`
	// Attributes are used to include tests in test plans.
	//
	// See Also:
	//   Test plans: test/plan/plan.proto
	Attributes []*Attribute `protobuf:"bytes,2,rep,name=attributes,proto3" json:"attributes,omitempty"`
	// Required conditions to be met for the Devices Under Test targeted by this
	// test.
	//
	// Constraint enforcement is an optional feature for test scheduling, i.e.,
	// some Test Lab Environments may ignore conditions entirely.
	//
	// If the test execution is sharded over multiple devices, each must satisfy
	// these conditions.
	DutConstraint *DUTConstraint `protobuf:"bytes,6,opt,name=dut_constraint,json=dutConstraint,proto3" json:"dut_constraint,omitempty"`
	// Metadata about the test that doesn't affect scheduling.
	Informational *Informational `protobuf:"bytes,4,opt,name=informational,proto3" json:"informational,omitempty"`
	// Will be deleted (& reserved) once all clients have migrated.
	//
	// Deprecated: Do not use.
	DutCondition *DUTCondition `protobuf:"bytes,5,opt,name=dut_condition,json=dutCondition,proto3" json:"dut_condition,omitempty"`
	// contains filtered or unexported fields
}