This page is intended as a working draft of how we will look to leverage and develop test cases for the dovetail project.
here it is the framework of dovetail( including some information from C&C)
Deliverers for the dovetail
- Test cases( dovetail will not focus on and define the API)
- Scripts for validating the test cases
The dovetail test suite
The dovetail test suite is intended to provide a method for validating the interfaces and behaviors of an NFVi platform according to the expected capabilities exposed in an OPNFV NVFi realization. All dovetail tests will be available in open source and will be developed on readily available open source test frameworks.
...
Dovetail should initially set out to provide validation of interfaces and behaviors common to an OPNFV NVFi. This can be seen as a set of test cases that evaluate if a NVFi implementation is able to achieve a steady operational state covering the common behaviors expected of an OPNFV NFVi. In this case the dovetail tests will focus on a SUT definition of VNFi & VIM as described in 4.9 of the ETSI NFV TST 001 specification.hongbo: Dovetail is not focusing on the validation of the interfaces......the dovetail is focusing on the test cases for value of OPNFV platform. in this case, the dovetail will go after the OPNFV release since the OPNFV release has the stable value of the OPNFV. for the phase1, the dovetail will show the value of the C release.
Dovetail phase 2
Dovetail should further establish a set of test suites that validate additional desired OPNFV VNFi behaviours. This may include for instance, deployment specific capabilities for edge or remote installations. It may include the validation of functionality that is not yet common to all OPNFV VNFi scenario's.
In phase 2 it may also be possible that dovetail provides such services as application test suites to validate the behavior of applications in preparation for deployment on an OPNFV VNFi. This may result in the definition of new SUT scopes for dovetail as described in of the ETSI NFV TST 001 specification.hongbo: the phase 2 will show the value of the D release.
Dovetail phase 3
hongbo: the same as those defined in the phase 1 and phase 2
Out of scope (I left this for now, but it does not belong on this page)
Dovetail is not a testing problem with a goal of identifying gaps in the platform. Its goal is to validate the conformance of OPNFV "stacks" to a minimum set of capabilities common to all OPNFV implementations. As such, it is not a goal of the Dovetal project to write failing tests, or to engage in the development of APIs to fill perceived gaps in the platform. While formulating the Dovetail test suite, it is possible that we will encounter limits of the commonalities of OPNFV implementations in areas which we would like to test conformance. In this case, efforts to create alignment, or to implement missing features, should happen in the context of other OPNFV projects. Dovetail will always be primarily concerned with documenting and verifying common platform capabilities after they exist.
hongbo: as we discussed in the dovetail meeting, the goal of the dovetail is to clearly articulates meaning of the brand/value proposition from C&C . in this case, the dovetail needs to implements the requirements from C&C by outputting the deliverable in terns of testcases and scripts. in order to do that, the dovetail can choose the test cases and scripts from the OPNFV test projects but not limited to the test projects. it is obviously that the certification defined by the dovetail will show the value of OPNFV which exist in the OPNFV platform.
...