Created the initial structure for the plugfest test plan.
* Created a base directory and document structure
* Created contributor guidelines
* Created test case template
* adjusted for: http://artifacts.opnfv.org/releng/docs/how-to-use-docs/documentation-example.html
* cp: reformatted the directories and structure to use the RST format
* (we cannot review odt format in our toolchain, so use rst)
* cp: added an index.rst structure to establish structure without numbering
* cp: will ad anothe job to include dovetail in the docs toolchain
Change-Id: I4ef997da51b3b85e391629d6e08fadf87257fc6a
--- /dev/null
+This directory contains the test plan being developed by the OPNFV Dovetail
+project team for the plugfest test events. The test plan is broken up into
+files containing its individual sections to allow developers to easily
+collaborate, without causing collisions.
+
+Developer Guidelines
+1. Please check with a project leader before creating a new directory.
+2. Please use a number scheme for file names to logical order the files as
+ the document should read when a “natural sort” operation is applied.
+3. The LibreOffice format has been selected to provide a file format that
+ allows the inclusion of figures, pictures, and tables. Please keep all
+ files in this format, or as a raw text file.
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+===============================
+Dovetail integration test cases
+===============================
+
+.. This file includes test cases for VNF application deployment on the OPNFV platform.
+
+.. The setup.rst file organises and imports the relevant RST files in this
+.. directory and includes them in the overall plugfest documentation.
+
+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.
+
+.. toctree::
+ :maxdepth: 2
+
+ ./testcase1.rst
+ ./testcase2.rst
+ ./testcase_etc.rst
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+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”.
+
+.. _ETSI: http://www.etsi.org/
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+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.
+
+.. _ETSI: http://www.etsi.org/
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+==============================
+Dovetail deployment test cases
+==============================
+
+.. This file includes the test cases specific to the OPNFV deployment testing.
+
+.. The setup.rst file organises and imports the relevant RST files in this
+.. directory and includes them in the overall plugfest documentation.
+
+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.
+
+.. toctree::
+ :maxdepth: 2
+
+ ./testcase1.rst
+ ./testcase2.rst
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+**************************
+OPNFV Plugfest - test plan
+**************************
+
+.. This index.rst file is used to structure and organise the content in these directories.
+.. The documentation toolchain will create web and pdf versions of the content of this file.
+
+.. toctree::
+ :maxdepth: 2
+
+ ./preface
+ ./setup/setup.rst
+ ./deployment/testcases.rst
+ ./integration/testcases.rst
+ ./application/testcases.rst
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+===============================
+Dovetail integration test cases
+===============================
+
+.. This file includes test cases for testing integration
+.. between the OPNFV platform and network equipment (i.e. SDN Controllers,
+.. Routers, etc.).
+
+.. The setup.rst file organises and imports the relevant RST files in this
+.. directory and includes them in the overall plugfest documentation.
+
+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.
+
+.. toctree::
+ :maxdepth: 2
+
+ ./testcase1.rst
+ ./testcase2.rst
+ ./testcase_etc.rst
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+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.
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+================================
+Plugfest setup and configuration
+================================
+
+.. This directory includes files and information for the test
+.. equipment, setup, configuration, and other general items that apply
+.. to multiple test cases.
+
+.. The setup.rst file organises and imports the relevant RST files in this
+.. directory and includes them in the overall plugfest documentation.
+
+We can add some general text here introducing the setup and configuration
+before digging into the details of each of the necessary sub chapters.
+
+.. toctree::
+ :maxdepth: 2
+
+ ./testframeworkconfig.rst
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+---------------------------------------
+Configuring the dovetail test framework
+---------------------------------------
+
+.. This file should outline how to configure the test framework for DoveTail
+
+Text required to be added here regarding the test framework configuration.
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+Test case title
+---------------
+
+Purpose
+^^^^^^^
+
+Description of the intended purpose of the test case.
+Purpose may also describe the cause/need of the test case,
+such as, describing a specific high availability failover cause.
+
+References
+^^^^^^^^^^
+
+Pointer to specific reference in standard, architecture, or other documentation.
+
+Test Setup
+^^^^^^^^^^
+
+1. List of equipment or software specific to this test case.
+2. List of steps required to prepare the devices / network for testing.
+3. These steps need to be performed only once.
+
+Method of Procedure
+^^^^^^^^^^^^^^^^^^^
+
+1. List of steps to perform the actual test case
+2. These steps might be performed multiple times, if a retest is required.
+
+Expected Results
+^^^^^^^^^^^^^^^^
+
+1. List of specific results expected from the procedure.
+2. These results / test metrics are used to indicate the pass/fail status for the test case.
+3. To pass a test case, it all individual metrics would be expected to “pass.”
+
Code Review / dovetail.git / commitdiff