Brief Project Overview (brief as it should be known)
The current ONAP VTP project as a test framework provided basic testing capabilities. It integrates a part of test cases, which are relatively simple (such as VNFP check, VNFD basic syntax check, etc.) and the more complex VNF and NFVI test procedures are not currently available in VTP.
To achieve a more flexible NFV automated test platform, ONAP-based NFV automatic testing platform provides a flexible testing framework for testers, and enables output customized test reports (e.g. XML, Json, etc.).
New component capabilities for Guilin, i.e. the functional enhancements, if applicable
- Enhance VTP and CLI to support:
- Test instruments integration:
(1) Test Case execution;
(2) Test Case discovering and auto registration;
(3) Robot profile integration.
2.VTP capability expansion:
(1)Loading different test scripts and cases- Scenario Active Management ;
(2)Flexible test process definition(Middle);
(3)Test report customization
(4) Profile HTTP API support
3. Execution-Standard / Open source test case support
(1) Enable ETSI NFV APIs conformance test cases in VTP;
(2) Enable CNCF CNF conformance test case in VTP.
New or modified interfaces
If they are modified, are they backwards compatible?
Interface naming (point to an example)
Consumed API from other projects
Project | API Dependency | Notes |
---|---|---|
Published API
Project | API | Notes |
---|---|---|
Reference to the interfaces.
(Reference to the the swagger.json file(s) whenever possible)
What are the system limits?
.
Involved use cases, architectural capabilities or functional requirements.
Listing of new or impacted models used by the project (for information only).
(list all the relevant Jira tickets)