...
- validation and display of test results (see also terminology below)
- the web portal must validate uploaded test results by comparing the "test result summary" to a "test result guideline"
- "test result guideline": source of truth
- list of all test cases which are part of a given OVP release
- use case: detect if test cases are missing from uploaded test results
- the expected result for passing each test case (functional tests: "pass", non-functional: "value")
- stored in web portal only
- list of all test cases which are part of a given OVP release
- "test result summary"
- part of the "test result package" generated by test tool
- json formatted
- should include in addition to today (AP on test tooling team)
- OVP release ID (e.g. 2020.10)
- OVP program type (e.g. NVFI, VNF, ...)
- example of a "test result package" currently generated by test tooling:
- "test result guideline": source of truth
- optional requirements, requires close collaboration with and input from test tooling team
- define a schema for formal validation of test result summary
- define a schema for formal validation of test result guide
- the web portal must validate uploaded test results by comparing the "test result summary" to a "test result guideline"
- portal lifecycle management
- all management operations on test results, market place entries, users, and new releases of OVP must be runtime operations not requiring new builds of the web portal
- separation of LCM of the portal instance (responsibility of LF IT) and content (responsibility of OVP admins)
...