directory update

JIRA: DOVETAIL-395

1. since plugfest has its own plan, the files are removed

Change-Id: I4989d1e0e1af483205733b3130e3f1152a8933c7
Signed-off-by: hongbotian <hongbo.tianhongbo@huawei.com>

3 files changed, 0 insertions, 101 deletions

diff --git a/docs/plugfest/2016.05/test_plan/deployment/testcase1.rst b/docs/plugfest/2016.05/test_plan/deployment/testcase1.rst
deleted file mode 100644
index f583729a..00000000
--- a/docs/plugfest/2016.05/test_plan/deployment/testcase1.rst
+++ /dev/null
@@ -1,39 +0,0 @@
-.. 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/
diff --git a/docs/plugfest/2016.05/test_plan/deployment/testcase2.rst b/docs/plugfest/2016.05/test_plan/deployment/testcase2.rst
deleted file mode 100644
index 579bbe7b..00000000
--- a/docs/plugfest/2016.05/test_plan/deployment/testcase2.rst
+++ /dev/null
@@ -1,40 +0,0 @@
-.. 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/
-
diff --git a/docs/plugfest/2016.05/test_plan/deployment/testcases.rst b/docs/plugfest/2016.05/test_plan/deployment/testcases.rst
deleted file mode 100644
index bb8dc9d1..00000000
--- a/docs/plugfest/2016.05/test_plan/deployment/testcases.rst
+++ /dev/null
@@ -1,22 +0,0 @@
-.. 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
-