This page is intended as a working draft of how we will look to leverage and develop test cases for the dovetail project.
...
Working with the ETSI NFV TST 001 reference: http://www.etsi.org/deliver/etsi_gs/NFV-TST/001_099/001/01.01.01_60/gs_NFV-TST001v010101p.pdf
Where I would see our dovetail project focus on SUT tests validating a SUT scope associated with Chapter 4.9 - NFV Infrastructure + VIM Under Test as adapted for OPNFV see figure below. While we may also look at interesting use cases like SFC, I would suggest we have clear plan on pre-deployment validation to ensure that any platform we are evaluating is first evaluated to be in a steady state of readiness.
Aside from the very basic requirements we would have on a test case to be used in dovetail:
...
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.
...