WARNING: This page is not currently maintained. Test areas will be defined in the test strategy document (being developed in this Gerrit proposal and tracked in this JIRA ticket - see current draft document), and specific test cases will be discussed and included in the Dovetail JIRA and Gerrit repository
This is the list of candidate test areas which have been proposed by community members for addition to the Dovetail test suite. These test areas will be evaluated under the Dovetail test case requirements, proposed for inclusion as patches in Gerrit against Dovetail, and reviewed by the Dovetail maintainers. Once approved, they will become part of the Dovetail test suite.
Brainstorming
This section is intended to help us get to quick consensus on the test priorities for Danube. The rest of the content of this page will be updated to be aligned with this section.
This is intended to help us discuss and collaboratively edit a set of priorities for the dovetail program in OPNFV.
- This is itself a strawman proposal for how we can discuss this important topic. Alternatives are welcome, although the basic goal is that we can come to collaborative consensus as quickly as possible, with minimal barriers to participation in the discussion.
Also see:
High
- Component verification: leverage all available tests to validate functional/API/etc capabilities of component distros
- NFVI+VIM: start with well-established aspects of NFVI+VIM
- Reference VNF portability: demonstrate portability and consistent operation for an ever-expanding suite of reference VNFs, which have been verified for most/all OPNFV distros
- Cross-controller dependent OPNFV features: verify operation of features that depend upon coordinated use of multiple components
- Broadly supported OPNFV features: focus on features that are support in many/most distros and hardware platforms
Medium
- Reliability: operation/performance under stress e.g. load and chaos
- Performance: benchmarking
- Security: static scans (vulnerabilities, licenses) and response to threats in operation
- Infra lifecycle: deployment and day-2 operations
Low
- Narrowly-supported features: any features that are distro or hardware platform specific
- Application (e.g. VNF) compliance with standards: while we may leverage reference VNFs as typical use cases their use should focus entirely upon verifying that the NFVI etc implementations result in a consistent user experience. The "user" in this case is the service provider, and consistency does not extend to whether the VNF itself or how it is operated adheres to any standards-based expectation on functionality.
Details on Test Areas
VIM Operations on Compute
...