|
|
| (20 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| = Requirements =
| | Fedora CI metadata specification moved to https://pagure.io/fedora-ci/metadata. |
| | |
| In order to use [[Flexible_Metadata_Format|Flexible Metadata Format]] effectively for the OSCI testing we need to agree on the essential set of attributes to be used. For each attribute we need to standardize:
| |
| | |
| * Name (unique, well chosen, possibly with a prefix)
| |
| * Type (expected content type: string, number, list, dict)
| |
| * Purpose (detailed description of the attribute purpose)
| |
| | |
| For names we should probably consider using namespace prefix (such as test-description, requirement-description) to prevent future collisions with other attributes. Each attribute definition should contain at least one apt example of the usage.
| |
| | |
| = Attributes =
| |
| | |
| In this section there are proposed attributes. Material for discussion. Nothing final for now.
| |
| | |
| == Summary ==
| |
| | |
| In order to efficiently collaborate on test maintenence it's
| |
| crucial to have for each test at lest a short summary of what the
| |
| test does.
| |
| | |
| * name: summary, test-summary
| |
| * type: string (recommend 50 characters or less like for [https://stackoverflow.com/questions/2290016/git-commit-messages-50-72-formatting commits]?)
| |
| | |
| == Description ==
| |
| | |
| == Tags ==
| |
| | |
| * Name: tags
| |
| * Type: list
| |
| * Purpose: free-form tags for easy filtering
| |
| | |
| == Test ==
| |
| | |
| == Path ==
| |
Latest revision as of 14:15, 18 October 2018
