Re-Structuring the directory for more better understanding of test types

Change-Id: I9284eb7ddaf727eef2d107e1e886fc60ec760446
Signed-off-by: Shwetha Panduranga <spandura@redhat.com>

4 files changed, 67 insertions, 1 deletions

diff --git a/tests/README.txt b/tests/README.txt
index 9f8dc8073..c2b950367 100644
--- a/tests/README.txt
+++ b/tests/README.txt
@@ -1 +1 @@
-Place test directories and files here
\ No newline at end of file
+Place test directories and files here
diff --git a/tests/functional/README b/tests/functional/README
new file mode 100644
index 000000000..07d029dd4
--- /dev/null
+++ b/tests/functional/README
@@ -0,0 +1,21 @@
+Functional Testing:
+    Process of validating that the software conforms to its specifications and
+    correctly performs its required functions.
+
+    This entails a series of feature by feature validation of behavior using
+    a wide range of normal and erroneous input data.
+
+    Functional testing divided in 3 categories:
+    - Build Validation tests:
+        Build Verification Test (BVT), also known as Build Acceptance Test,
+        is a set of tests run on each new build of a software to verify that
+        the build is testable before the build is released into further testing.
+
+    - Smoke Testing:
+        A subset of test cases that are designed to broadly and minimally
+        test to confirm that changes in the code of a particular build
+        function as expected and do not break an entire build.
+
+    - Regression:
+        Process of retesitng a build after bug fixes and code changes to
+        find any unexpected loss of functionality in the new code base.
diff --git a/tests/functional/bvt/README b/tests/functional/bvt/README
new file mode 100644
index 000000000..5efc3bca3
--- /dev/null
+++ b/tests/functional/bvt/README
@@ -0,0 +1,45 @@
+What is Build Verification or Build Validation Test?
+    In software testing, a Build Verification Test (BVT), also known as
+    Build Acceptance Test, is a set of tests run on each new build of a product
+    to verify that the build is testable before the build is released into the
+    hands of the test team.
+
+Scope of Testing:
+    The build acceptance test is generally a short set of tests,
+    which exercises the mainstream functionality of the application software.
+    Any build that fails the build verification test is rejected,
+    and testing continues on the previous build (provided there has been at
+    least one build that has passed the acceptance test)
+
+Source of definition: https://en.wikipedia.org/wiki/Build_verification_test
+
+Gluster BVT: BVT is divided in 2 set of tests.
+    - BVT-Basic :
+        BVT-Basic is the first set of tests to qualify the build.
+        Tests include validating services (glusterd, smb etc),
+        validating volume operations (create, start, stop , status)
+
+    - BVT-VVT ( VVT: Volume verification test)
+        BVT-VVT is the second set of tests to qualify whether the build is good to
+        be consumed for further testing once BVT-Basic passes.
+        BVT-VVT covers the following gluster specific test on all combinations
+        of volume and mount types supported by gluster.
+
+        Test Case Summary:
+            1) Creates a volume
+            2) Mounts the volume
+            3) Run IO from the mount.
+            4) teardown the mount
+            5) teardown the volume
+
+        Volume types:
+            - Distribute
+            - Replicate
+            - Distribute-Replicate
+            - Disperse
+            - Distribute-Disperse
+
+        Mount types:
+            - Glusterfs
+            - Nfs
+            - CIFS
diff --git a/tests/bvt/test_bvt_lite_and_plus.py b/tests/functional/bvt/test_bvt_lite_and_plus.py
index 55db725b9..55db725b9 100644
--- a/tests/bvt/test_bvt_lite_and_plus.py
+++ b/tests/functional/bvt/test_bvt_lite_and_plus.py