Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Working with the ETSI NFV TST 001reference001 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.  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:

  • Test cases should implement a published standard interface for validation
    • Where no standard is available provide API support references
    • If a standard exists is not followed an exemption method needs to be established
  • Test cases be documented
    • Use case specification
    • Test preconditions
    • Basic test flow execution descriptor
    • Post conditions and pass fail criteria
    • Parameter border test cases descriptions
    • Fault/Error test case descriptions  (this feels optional at this time)
  • Test cases must pass on OPNFV reference deployments
    • Tests must pass with deployments with at least two installers
    • Tests must pass with at least two deployment scenarios involving difference SDN controllers
  • Test documentation/implementation file and directory structure (per supported framework)
  • Test result storage, structure and test result information management (these should be able to be run publically or privately)

...

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.

Dovetail phase 3

Out of scope

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.