1# Harness-specific metadata 2 3Sub-directories in this directory house protobuf definitions specific to various 4Remote Test Drivers (RTD). 5 6e.g., [tauto/v1/tauto.proto](tauto/v1/tauto.proto) contains a message that 7serves as the schema for the payload in [metadata.Information.Details] field 8of test metadata for Tauto tests. 9 10The test plans and test scheduling infrastructure *MUST NOT* depend on these 11definitions. 12 13Defining the schema for [metadata.Information.Details] payload here has the 14following benefits: 15 16- Provides strongly typed parsing of [metadata.Information.Details] at RTD 17 execution to modify behavior of the RTD based on test metadata. 18 19- Provides a way to build additional RTD specific analytics solutions from the 20 test metadata exported from the Continuous Integration infrastructure. 21 22 - The RTD specific analytics pipelines can build data transformation steps for 23 backwards compatibility, similar to that for the generic metadata. 24 25[metadata.Information.Details]: https://chromium.googlesource.com/chromiumos/config/+/6011eafe2029936dae767a7f75fdb965782006fa/proto/chromiumos/config/api/test/metadata/v1/metadata.proto#423