From 222892c2db2b03d615064368981f4c0168216474 Mon Sep 17 00:00:00 2001
From: tdubyk <tdubyk@mirantis.com>
Date: Thu, 2 Oct 2014 12:18:05 +0300
Subject: [PATCH] Add spec for nsx and vcenter autotests

Enable support of automated acceptance test cases for vCenter and NSX features.
This will allow as to perform full scale acceptance testing of our
features in short time, according to manual test cases of these features
blueprint  nsx-vcenter-system-tests-smoke

Change-Id: Idad4b098f59894ae4624f5071a3f4ff2f807363a
---
 specs/6.0/nsx-vcenter-system-tests-smoke.rst | 124 +++++++++++++++++++
 1 file changed, 124 insertions(+)
 create mode 100644 specs/6.0/nsx-vcenter-system-tests-smoke.rst

diff --git a/specs/6.0/nsx-vcenter-system-tests-smoke.rst b/specs/6.0/nsx-vcenter-system-tests-smoke.rst
new file mode 100644
index 00000000..7aed800b
--- /dev/null
+++ b/specs/6.0/nsx-vcenter-system-tests-smoke.rst
@@ -0,0 +1,124 @@
+==================================================================
+Integration of automated system tests for NSX and vCenter features
+==================================================================
+
+Related to blueprint:
+https://blueprints.launchpad.net/fuel/+spec/nsx-vcenter-system-tests-smoke
+
+Problem description
+===================
+
+We have a lot of acceptance and smoke test cases for NSX and vCenter features,
+but we haven't got enough time to perform it manually during feature freeze
+milestone.
+
+Proposed change
+===============
+
+Enable support of automated system tests which are based on manual
+acceptance test cases of vCenter and NSX features.
+It will allow us to reduce the time to perform a comprehensive acceptance
+testing, according to manual test cases that we've already created
+considering different parameters and modes.
+
+Alternatives
+------------
+
+If it is not implemented in time, we will perform only manual tests with
+'High' priority.
+
+Data model impact
+-----------------
+
+None.
+
+REST API impact
+---------------
+
+None.
+
+Upgrade impact
+--------------
+
+None.
+
+Security impact
+---------------
+
+None.
+
+Notifications impact
+--------------------
+
+None.
+
+Other end user impact
+---------------------
+
+None.
+
+Performance Impact
+------------------
+
+As non functional type of testing, we will check what kind of performance
+impact NSX can have on lab.
+
+Other deployer impact
+---------------------
+
+None.
+
+Developer impact
+----------------
+
+None.
+
+
+Implementation
+==============
+
+Assignee(s)
+-----------
+
+Primary assignee:
+
+* Tatyana Dubyk (tatka.donets)
+
+Other contributors:
+
+* Alexander Kosse (al.rem)
+* Eugene Korekin (azkore)
+
+Work Items
+----------
+
+* Create automated system tests according to manual acceptance test
+  cases with different configuration and parameters for nsx and
+  vcenter features, to check that nsx and vcenter features are successfully
+  integrated with each other;
+* Verify that according to blueprints of this release our features with
+  additional settings that are in scope of release work fine;
+* Set up a test environment and debug tests on host, that is allocated for it;
+* Add these tests in already existing Jenkins jobs.
+
+Dependencies
+============
+
+None.
+
+Testing
+=======
+
+Check that all tests are implemented according to the required workflow
+and they run stably in Jenkins jobs.
+
+Documentation Impact
+====================
+
+All additional information related to nsx you can find there:
+http://goo.gl/3Klbq3
+
+References
+==========
+
+None.
\ No newline at end of file