Skip to end of banner
Go to start of banner

Testing Evolution & Strategy

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

This page is intended to capture discussions and work relating to the longer term strategy and direction of testing within the LFN programs.

Testing Scopes

Note, the following is a work in progress.

VNF Testing

  • Compliance:

    • Conformance to HEAT or TOSCA Templates, as defined by ONAP Requirements.

    • Documentation of VNF is available.

  • Validation:

    • On-boarding: Validate the VNF Artifact(s) is able to be "consumed" by an ONAP instance.

      • Open questions: 1) What are the requirements defined for "On-boarding?" What is the requirement for the "ONAP instance?" 3) Is there a requirement for backwards compatibility?

    • Instantiation: Validate the VNF can be "launched" by an ONAP instance on top of an NFVI.

      • Open questions: 1) What is the requirements for ONAP Instance? 2) What is the requirements for the NFVI? 3) What are the requirements for the "VNF launch?"

    • Validate various life-cycle operations are possible with the VNF running on the ONAP Instance.

      • Open questions: 1) What the required "life-cycle operations?" 2) What the requirements for each "operation?" 3) What are the requirements for the "ONAP instance?"

  • Performance:

    • Capacity:

    • Stability:

  • Security:

    • Open question: Where do these requirements come from? Who is responsible for the test cases?

NFVI Testing

  • Compliance:

  • Validation:

  • Performance:

Related Attachments and Presentations

  File Modified
No files shared here yet.

  • No labels