summaryrefslogtreecommitdiffstats
path: root/docs/testing/user/testspecification/vping/index.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/testing/user/testspecification/vping/index.rst')
-rw-r--r--docs/testing/user/testspecification/vping/index.rst101
1 files changed, 59 insertions, 42 deletions
diff --git a/docs/testing/user/testspecification/vping/index.rst b/docs/testing/user/testspecification/vping/index.rst
index 6ba29a1..355018c 100644
--- a/docs/testing/user/testspecification/vping/index.rst
+++ b/docs/testing/user/testspecification/vping/index.rst
@@ -3,7 +3,7 @@
.. (c) Ericsson AB
========================
-Vping test specification
+Vping Test Specification
========================
.. toctree::
@@ -34,7 +34,7 @@ References
- https://pypi.org/project/scp/
-Definitions and abbreviations
+Definitions and Abbreviations
=============================
The following terms and abbreviations are used in conjunction with this test
@@ -42,10 +42,10 @@ area
- ICMP - Internet Control Message Protocol
- L3 - Layer 3
-- NFVi - Network functions virtualization infrastructure
-- SCP - Secure Copy
-- SSH - Secure Shell
-- VM - Virtual machine
+- NFVi - Network Functions Virtualization infrastructure
+- SCP - Secure CoPy
+- SSH - Secure SHell
+- VM - Virtual Machine
System Under Test (SUT)
@@ -73,7 +73,7 @@ Test Case 1 - vPing using userdata provided by nova metadata service
Short name
----------
-dovetail.vping.userdata
+functest.vping.userdata
Use case specification
@@ -106,39 +106,46 @@ checking the console output of the source VMs.
Test execution
''''''''''''''
-* Test action 1:
+* **Test action 1:**
* Create a private tenant network by using neutron client
* Create one subnet and one router in the network by neutron client
* Add one interface between the subnet and router
* Add one gateway route to the router by neutron client
* Store the network id in the response
* **Test assertion 1:** The network id, subnet id and router id can be found in the response
-* Test action 2:
+* **Test action 2:**
* Create an security group by using neutron client
* Store the security group id parameter in the response
* **Test assertion 2:** The security group id can be found in the response
-* Test action 3: boot VM1 by using nova client with configured name, image, flavor, private tenant
- network created in test action 1, security group created in test action 2
+* **Test action 3:**
+ * Boot VM1 by using nova client with configured name, image, flavor, private tenant
+ network created in test action 1 and security group created in test action 2
* **Test assertion 3:** The VM1 object can be found in the response
-* Test action 4: Generate ping script with the IP of VM1 to be passed as userdata provided by
- the **nova metadata service**.
-* Test action 5: Boot VM2 by using nova client with configured name, image, flavor, private tenant
- network created in test action 1, security group created in test action 2, userdata created
- in test action 4
+* **Test action 4:**
+ * Generate ping script with the IP of VM1 to be passed as userdata provided by
+ the **nova metadata service**
+* **Test action 5:**
+ * Boot VM2 by using nova client with configured name, image, flavor, private tenant
+ network created in test action 1, security group created in test action 2, and
+ userdata created in test action 4
* **Test assertion 4:** The VM2 object can be found in the response
-* Test action 6: Inside VM2, the ping script is executed automatically when booted and it contains a
- loop doing the ping until the return code is 0 or timeout reached. For each ping, when the return
- code is 0, "vPing OK" is printed in the VM2 console-log, otherwise, "vPing KO" is printed.
- Monitoring the console-log of VM2 to see the response generated by the script.
+* **Test action 6:**
+ * Inside VM2, the ping script is executed automatically when booted and it contains a
+ loop doing the ping until the return code is 0 or timeout reached
+ * For each ping, when the return code is 0, "vPing OK" is printed in the VM2 console-log,
+ otherwise, "vPing KO" is printed
+ * Monitoring the console-log of VM2 to see the response generated by the script
* **Test assertion 5:** "vPing OK" is detected, when monitoring the console-log in VM2
-* Test action 7: delete VM1, VM2
+* **Test action 7:**
+ * Delete VM1, VM2
* **Test assertion 6:** VM1 and VM2 are not present in the VM list
-* Test action 8: delete security group, gateway, interface, router, subnet and network
+* **Test action 8:**
+ * Delete security group, gateway, interface, router, subnet and network
* **Test assertion 7:** The security group, gateway, interface, router, subnet and network are
no longer present in the lists after deleting
-Pass / fail criteria
+Pass / Fail criteria
''''''''''''''''''''
This test evaluates basic NFVi capabilities of the system under test.
@@ -173,7 +180,7 @@ Test Case 2 - vPing using SSH to a floating IP
Short name
----------
-dovetail.vping.ssh
+functest.vping.ssh
Use case specification
@@ -207,45 +214,55 @@ Test execution
''''''''''''''
-* Test action 1:
+* **Test action 1:**
* Create a private tenant network by neutron client
* Create one subnet and one router are created in the network by using neutron client
* Create one interface between the subnet and router
* Add one gateway route to the router by neutron client
* Store the network id in the response
* **Test assertion 1:** The network id, subnet id and router id can be found in the response
-* Test action 2:
+* **Test action 2:**
* Create an security group by using neutron client
* Store the security group id parameter in the response
* **Test assertion 2:** The security group id can be found in the response
-* Test action 3: Boot VM1 by using nova client with configured name, image, flavor, private tenant
- network created in test action 1, security group created in test action 2
+* **Test action 3:**
+ * Boot VM1 by using nova client with configured name, image, flavor, private tenant
+ network created in test action 1 and security group created in test action 2
* **Test assertion 3:** The VM1 object can be found in the response
-* Test action 4: Boot VM2 by using nova client with configured name, image, flavor, private tenant
- network created in test action 1, security group created in test action 2
+* **Test action 4:**
+ * Boot VM2 by using nova client with configured name, image, flavor, private tenant
+ network created in test action 1 and security group created in test action 2
* **Test assertion 4:** The VM2 object can be found in the response
-* Test action 5: create one floating IP by using neutron client, storing the floating IP address
- returned in the response
+* **Test action 5:**
+ * Create one floating IP by using neutron client, storing the floating IP address
+ returned in the response
* **Test assertion 5:** Floating IP address can be found in the response
-* Test action 6: Assign the floating IP address created in test action 5 to VM2 by using nova client
+* **Test action 6:**
+ * Assign the floating IP address created in test action 5 to VM2 by using nova client
* **Test assertion 6:** The assigned floating IP can be found in the VM2 console log file
-* Test action 7: Establish SSH connection between the test host and VM2 through the floating IP
+* **Test action 7:**
+ * Establish SSH connection between the test host and VM2 through the floating IP
* **Test assertion 7:** SSH connection between the test host and VM2 is established within
300 seconds
-* Test action 8: Copy the Ping script from the test host to VM2 by using SCPClient
+* **Test action 8:**
+ * Copy the Ping script from the test host to VM2 by using SCPClient
* **Test assertion 8:** The Ping script can be found inside VM2
-* Test action 9: Inside VM2, to execute the Ping script to ping VM1, the Ping script contains a
- loop doing the ping until the return code is 0 or timeout reached, for each ping, when the return
- code is 0, "vPing OK" is printed in the VM2 console-log, otherwise, "vPing KO" is printed.
- Monitoring the console-log of VM2 to see the response generated by the script.
+* **Test action 9:**
+ * Inside VM2, to execute the Ping script to ping VM1, the Ping script contains a
+ loop doing the ping until the return code is 0 or timeout reached
+ * For each ping, when the return code is 0, "vPing OK" is printed in the VM2 console-log,
+ otherwise, "vPing KO" is printed
+ * Monitoring the console-log of VM2 to see the response generated by the script
* **Test assertion 9:** "vPing OK" is detected, when monitoring the console-log in VM2
-* Test action 10: delete VM1, VM2
+* **Test action 10:**
+ * Delete VM1, VM2
* **Test assertion 10:** VM1 and VM2 are not present in the VM list
-* Test action 11: delete floating IP, security group, gateway, interface, router, subnet and network
+* **Test action 11:**
+ * Delete floating IP, security group, gateway, interface, router, subnet and network
* **Test assertion 11:** The security group, gateway, interface, router, subnet and network are
no longer present in the lists after deleting
-Pass / fail criteria
+Pass / Fail criteria
''''''''''''''''''''
This test evaluates basic NFVi capabilities of the system under test.