Allow extension of data tables against test runs via 'table record' metadata #64
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To provide a way for users of TestArchiver to extend the data, add a
special metadata name table#<table-name>:{json-fields} where json-fields
is of format {"field1":"value1", "field2":"value2"} and has to
correspond exactly to the fields in the table-name table or naturally
an exception will be thrown.
The creation of the table is left to the user, as TestArchiver can not
know what the table is.
Add documentation to help clarify how the table#<table-name> metadata can be used to extend any information against a test run.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 name <table_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 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.