The following is the proposal for the information model (i.e. required bits) for test results and tooling used in the badging.
| Parameter | Status | Description |
|---|
For each budge submission This information would be collected from the submitter, when the results are submitted for review to the program. A likely approach will be use of a template in the merge request comment, that makes the specific fields clear to the submitter. |
| Applicant Information | Mandatory | - Submitting Vendor Name
- Product Name
- Product Version
|
| Badge Information | Mandatory | The following are "pick from list" type values, where there are only specific values allowed, i.e. the in-force program / badge types and releases. - Badge Type (i.e. Cloud Native or NFV, Infrastructure or Workload)
- Budge Sub-Type (i.e. ONAP, CNCF, etc.)
- Badge Version / Release
|
| For each set of results generated |
| Results ID | Mandatory | - Uniquely identifies the set of test results generated during the test run.
- Must include:
|
Badge Type (Cloud Native or VM) Type (i.e. ONAP, Anuket Interop, CNCF) Test | Tool Details | Mandatory | - Must list the tool name, including the project originator / owner (i.e. ONAP or Anuket).
- Version of the tool.
- This must contain enough information, a user could reproduce the exact test run with the same test tooling.
|
| SUT Information |
Submitting Vendor Name| TBD | - Product Name
- Product Version
- Inventory
Notes: - Need to confirm what information is collected / stored by the tooling.
|
| For each test case included in submitted results |
| Test Case ID | Mandatory | - A unique identifier for the test case which has been executed.
|
It should be possible to use the Test Case ID to trace back to the specific requirement(s) that are covered by the unique test case- This must be a unique identifier across all projects and tests.
|
| Requirement ID | Optional | - Reference to requirement ID from the base project (i.e. VNF-REQTS).
- Requirements and test case implementations are driven by the individual communities.
|
This must be a unique identifier across all projects and tests.| Test Case Result | Mandatory | |
| Test Execution Log | TBD | - One or more files that capture logging and debugging output from the test run.
- The specific format of the files is undefined, and determined by the test tool.
- The link between the Test Case ID and log files MUST be clear, through either file naming or path locations.
|