Page tree
Skip to end of metadata
Go to start of metadata

The following test cases provide a basic description of each test, it's intended purpose, procedure, and metrics.  These test cases are intended to help guide the conversations between plugfests participants before and during the plugfest.  The test cases may also be used / included in the plugfest whitepaper, to help document to the industry some general information about the outcome(s) of the plugfest.


OPNFV Turn-up Scope

Basic Installer Test

Purpose:

To validate that each represented installer project has the opportunity to run deployment against each set of hardware provided.

Day to day validation of installer projects is often run against the same hardware. Running deployments on unfamiliar hardware validates that design of each project is portable across multiple vendor's hardware platforms.

Procedure:

A schedule will be constructed splitting up time across the installer projects and hardware sets.
Hardware information is expected to be posted on the wiki pages ahead of time offering installer project the opportunity to prepare any configuration needed ahead of time.
Installer projects will work with the hardware owners to execute deployment and test scripts.

Metrics / Expected Results:

  1. Installed OPNFV system is able to pass the basic "Smoke Test." Definition currently being derived from existing testing tools.

Scale I/O Test Case

Purpose:

  • TBD

Procedure:

  1. TBD

Metrics / Expected Results:

  1. TBD

SDN Integration Scope

  • TBD

VNF Applications Scope

VNF Package On-boarding Test Case

Purpose:

To verify a VNF application can be loaded and manually run on the OPNFV platform. This test may be repeated on various scenarios, with different OPNFV installers.

Procedure:

  1. Copy the VNF application files to the store on the OPNFV target platform.

  2. Create any networks / routers require for the VNF application.

  3. Start a new instance of the VNF application and monitor its start up for errors or failures.

Metrics / Expected Results:

  1. VNF is able to start and reach a stable state on the platform, without reporting any failures or errors.

  2. VNF is able reach any required or configured networks.

VNF Graceful Termination Test Case

Purpose:

To verify a VNF application can be shutdown without undue errors or negative impact to the platform.

Procedure:

  1. Use the VNF application interface to to request the VNF shutdown gracefully.

  2. Allow the application shutdown fully.

Metrics / Expected Results:

  1. The VNF is able to fully shutdown without reporting any failures or errors.

  2. VNF application is terminated and all memory and CPU allocations have been removed from the hypervisor.

  3. The shutdown does not impact the platform or any other running VNF applications.

VNF Forceful Termination Test Case

Purpose:

To verify the platform is able to terminate a VNF application, without interaction with the VNF software (i.e. support for the case were VNF application has internal fault).

Procedure:

  1. TBD

Metrics / Expected Results:

  1. VNF application is terminated and all memory and CPU allocations have been removed from the hypervisor.

  2. The shutdown does not impact the platform or any other running VNF applications.
     


Dovetail Testing Scope

 

  • No labels