summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkshithijiyer <kshithij.ki@gmail.com>2020-01-08 12:44:13 +0530
committerBala Konda Reddy M <bmekala@redhat.com>2020-01-08 07:35:40 +0000
commit0cbecf2763cf323a36e4b07ced7f436b1aeacb3f (patch)
tree7d8fb4c51610334f1638f7fbe8b343a641d8112b
parent4b34d0310d78f9d162689cf40a85a3d97d834218 (diff)
[Doc] Changing all text files to markdown files
Change-Id: I36949296607b09e66ce0a56029359481c0b76b8b Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
-rw-r--r--tests/README.md3
-rw-r--r--tests/README.txt1
-rw-r--r--tests/functional/bvt/README45
-rw-r--r--tests/functional/bvt/README.md51
-rw-r--r--tests/functional/nfs_ganesha/README.md (renamed from tests/functional/nfs_ganesha/README)21
5 files changed, 65 insertions, 56 deletions
diff --git a/tests/README.md b/tests/README.md
new file mode 100644
index 0000000..d519969
--- /dev/null
+++ b/tests/README.md
@@ -0,0 +1,3 @@
+# Tests directory
+
+Place test directories and files here.
diff --git a/tests/README.txt b/tests/README.txt
deleted file mode 100644
index c2b9503..0000000
--- a/tests/README.txt
+++ /dev/null
@@ -1 +0,0 @@
-Place test directories and files here
diff --git a/tests/functional/bvt/README b/tests/functional/bvt/README
deleted file mode 100644
index 5efc3bc..0000000
--- a/tests/functional/bvt/README
+++ /dev/null
@@ -1,45 +0,0 @@
-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/functional/bvt/README.md b/tests/functional/bvt/README.md
new file mode 100644
index 0000000..c2ac785
--- /dev/null
+++ b/tests/functional/bvt/README.md
@@ -0,0 +1,51 @@
+# BVT
+## 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/functional/nfs_ganesha/README b/tests/functional/nfs_ganesha/README.md
index 24c26df..d67544b 100644
--- a/tests/functional/nfs_ganesha/README
+++ b/tests/functional/nfs_ganesha/README.md
@@ -1,5 +1,6 @@
-Scope of Testing:
+# NFS Ganesha Tests
+Scope of Testing:
Nfs Ganesha functional tests includes test scripts specific to nfs ganesha
component such as high availability, nfsv4 acls, root squash, locks,
volume exports, subdirectory exports from client and server side, dynamic
@@ -8,14 +9,14 @@ refresh config.
Configs to change in glusto_tests_config.yml file for running the tests:
In cluster_config -> nfs_ganesha section,
- - Set enable: True
- - Give the number of nodes to participate in nfs ganesha cluster in
- integer format.
- - Virtual IPs for each nodes which will be part of nfs ganesha cluster
- in list format.
+- Set enable: True
+- Give the number of nodes to participate in nfs ganesha cluster in
+ integer format.
+- Virtual IPs for each nodes which will be part of nfs ganesha cluster
+ in list format.
In mounts section, for each mount
- - Set protocol to 'nfs'.
- - For v3 mount, set options: 'vers=3'
- - For v4 mount, set options: 'vers=4.0'
- - If 'options' is set to empty string, it takes v3 mount by default.
+- Set protocol to 'nfs'.
+- For v3 mount, set options: 'vers=3'
+- For v4 mount, set options: 'vers=4.0'
+- If 'options' is set to empty string, it takes v3 mount by default.