OPNFV Plugfest - test plan

Abstract

Describe in a few sentences the intention of this document, how it should be used and the intended audience.

Scope

Describe in a few sentences the intended scope of the document including any limitations and constraints the reader shoudl be aware of when reading the document.

Plugfest setup and configuration

We can add some general text here introducing the setup and configuration before digging into the details of each of the necessary sub chapters.

Configuring the dovetail test framework

Text required to be added here regarding the test framework configuration.

Dovetail deployment test cases

We can add some general text here around the deployment test cases. The test case descriptions should likely be organised as single rst files in this directory that are inported below the toctree command below.

Test case one

Purpose

This test case is the first and therefore most important test case. As the first you should take care to do all the set-up found in the `Plugfest setup and configuration`_ section.

References

Somewhere in ETSI there is a useful link.

Test Setup

  1. The number 1 is of special relevance to this test case.
  2. Do not stray to the number 2.
  3. This step needs to be performed only once.

Method of Procedure

  1. Count to one.
  2. Stop, if you counted further a retest is required.

Expected Results

  1. You arrived at 1.
  2. This results is used to indicate the pass/fail status for the test case executor.
  3. To pass a test case, it all individual metrics would be expected to “pass”.

Test case two

Purpose

This test case is the second and no one really cares for it. If you have it in you please refer to the `Plugfest setup and configuration`_ section, it’s OK to simply amble on at this stage. (It’s only the second test case)

References

Somewhere in ETSI there may be a useful link.

Test Setup

  1. The number 2 is kind of important.
  2. Try and get to the number 2.
  3. It’s OK if you only count to 1 we understand.

Method of Procedure

  1. Count to two.
  2. Stop, if you counted to something else we forgive you.

Expected Results

  1. You arrived at 2.
  2. This results is used to indicate the pass/fail status for the test case itself.
  3. To pass a test case, metrics would be expected to “pass” 1 and not stray to 3.

Dovetail integration test cases

We can add some general text here around the integration test cases. The test case descriptions should likely be organised as single rst files in this directory that are imported below the toctree command below.

Dovetail integration test cases

We can add some general text here around the application test cases. The test case descriptions should likely be organised as single rst files in this directory that are imported below the toctree command below.