The following is the proposal for the information model (i.e. required bits) for test results and tooling used in the badging.
Test Case Result
Badge ID LFN could provide unique id for every kind of badge
CNF URL Test Tool Details
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 |
|
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.
|
For each set of results generated | ||
Results ID | Mandatory |
|
Test Tool Details | Mandatory |
|
SUT Information | TBD |
Notes:
|
For each test case included in submitted results | ||
Test Case ID | Mandatory |
|
Requirement ID |
- Reference to Test case requirements – Part of RC2
- Test case requirements driven by ONAP communities
- Push to RC2 repo
Optional |
| |
Test Case Result | Mandatory |
|
Test Execution Log |
- It should support this test case result format while submitting it
TBD |
|