To allow extension of data tables against test runs, proposing the use of a special metadata tag, similar to series# and team#, namely table#<table_name> whose value is a json record defining the field to be written to a table with name .
For example a metadata entry
table#host_info:{"host_name":"test_machine01", "host_location":"Paris", "user":"James"}
would result in a record written to the database table host_info, with the json specified parameters host_name, host_location, user against TestArchiver's suite_id and test_run_id.
This will allow for extended information, specific to a test environment, to be defined as required by a test team.
TestArchiver would remain agnostic of this table and its contents, leaving the user to ensure the table is created via a different process and its field match the json data.
The full json value is also written to the metadata table as per any other metadata.
To allow extension of data tables against test runs, proposing the use of a special metadata tag, similar to.
series#andteam#, namelytable#<table_name>whose value is a json record defining the field to be written to a table with nameFor example a metadata entry
table#host_info:{"host_name":"test_machine01", "host_location":"Paris", "user":"James"}would result in a record written to the database tablehost_info, with the json specified parametershost_name, host_location, useragainst TestArchiver'ssuite_idandtest_run_id.This will allow for extended information, specific to a test environment, to be defined as required by a test team. TestArchiver would remain agnostic of this table and its contents, leaving the user to ensure the table is created via a different process and its field match the json data. The full json value is also written to the metadata table as per any other metadata.