Fix rendering on test plans (vmware#5643)

Author: singhshwetaQE

tests/manual-test-cases/Group11-Stress/11-1-VIC-Install-Stress.md

@@ -1,21 +1,21 @@
 Test 11-1 - VIC Install Stress
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the install component of the system
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. In a loop, install and delete a VCH appliance as rapidly as possible 100 times
 2. After the last install, run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 The VCH appliance should deploy without error each time and each of the docker commands executed against the last install should return without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-2-Container-Boot-Storm.md

@@ -1,23 +1,23 @@
 Test 11-2 - Container Boot Storm
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the container start component of the system
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. Create 100 container on the new VCH appliance
 3. In parallel, attempt to start all 100 containers at once
 4. After the boot storm, run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the containers should start without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-3-Many-Containers.md

@@ -1,22 +1,22 @@
 Test 11-3 - Many Containers
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of containers
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. In a loop, create 1000 containers using docker run busybox date
 3. After the last iteration, run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the containers should start without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-4-Many-Volumes.md

@@ -1,22 +1,22 @@
 Test 11-4 - Many Volumes
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of volumes
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. In a loop, create 1000 small volumes
 3. After the last iteration, run a variety of docker commands on the VCH appliance including creating a container that uses one of the volumes created in the loop
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the volume create commands should return without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-5-Many-Networks.md

@@ -1,22 +1,22 @@
 Test 11-5 - Many Networks
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of networks
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. In a loop, create 1000 networks
 3. After the last iteration, run a variety of docker commands on the VCH appliance including creating a container that uses one of the networks created in the loop
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the volume create commands should return without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-6-Stop-Storm.md

@@ -1,23 +1,23 @@
 Test 11-6 - Stop Storm
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of stop commands at once
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. Create 100 containers that keep running
 3. In parallel, attempt to stop each of the containers as quickly as possible
 4. Run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the volume stop commands should return without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-7-Remove-Storm.md

@@ -1,23 +1,23 @@
 Test 11-7 - Remove Storm
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of rm commands at once
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. Create 100 containers
 3. In parallel, attempt to rm each of the containers as quickly as possible
 4. Run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the volume rm commands should return without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-8-Image-Pull-Stress.md

@@ -1,22 +1,22 @@
 Test 11-8 - Image Pull Stress
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of image pull commands at once
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. Pull 100 images all at once, with at least 10 of the images pulled being the same image
 3. Run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 Each of the image pull commands should return without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group11-Stress/11-9-Container-Disk-Stress.md

@@ -1,23 +1,23 @@
 Test 11-9 - Container Disk Stress
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance works when stressing the appliance with a lot of disk operations
 
-#References:
+# References:
 None
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance into the vSphere server
 2. Create a container with a 10GB volume attached
 3. Within the container, execute bonnie++ disk stress test
 4. Run a variety of docker commands on the VCH appliance
 
-#Expected Outcome:
+# Expected Outcome:
 The bonnie++ command should return without error and at the end, the variety of docker commands run should work without error
 
-#Possible Problems:
-If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected
+# Possible Problems:
+If you exhaust the resources of the vSphere server, it is not necessarily a failure as long as the VCH appliance continues to function and behave as expected

tests/manual-test-cases/Group12-Maintenance-Mode/12-1-VIC-Machine-Maintenance-Mode.md

@@ -1,26 +1,26 @@
 Test 12-1 VIC Machine Maintenance Mode
 =======
 
-#Purpose:
+# Purpose:
 To verify the VIC appliance provides a reasonable error message when installing or deleting it from a host in maintenance mode
 
-#References:
+# References:
 [1- VMware Maintenance Mode](https://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.resourcemanagement.doc_41/using_drs_clusters_to_manage_resources/c_using_maintenance_mode.html)
 
-#Environment:
+# Environment:
 This test requires that a vSphere server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Put the vSphere server into maintenance mode
 2. Issue a vic-machine create command to attempt to install VIC into the server while it is in maintenance mode
 3. Instruct the vSphere server to exit maintenance mode
 4. Issue a vic-machine create command to install VIC into the server
 5. Instruct the vSphere server to enter maintenance mode
 6. Issue a vic-machine delete command to attempt to delete VIC from the server while it is in maintenance mode
 
-#Expected Outcome:
+# Expected Outcome:
 * For Step 2, the VCH appliance should deploy with an error that indicates the reason why it cannot install into a server in maintenance mode
 * For Step 6, the vic-machine delete command should return with an error indicating the reason why it cannot delete the VCH while the server is in maintenance mode
 
-#Possible Problems:
-None
+# Possible Problems:
+None

tests/manual-test-cases/Group13-vMotion/13-1-vMotion-VCH-Appliance.md

@@ -1,16 +1,16 @@
 Test 13-1 vMotion VCH Appliance
 =======
 
-#Purpose:
+# Purpose:
 To verify the VCH appliance continues to function properly after being vMotioned to a new host
 
-#References:
+# References:
 [1- vMotion A Powered On Virtual Machine](http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.dcadmin.doc_41/vsp_dc_admin_guide/migrating_virtual_machines/t_migrate_a_powered-on_virtual_machine_with_vmotion.html)
 
-#Environment:
+# Environment:
 This test requires that a vCenter server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance onto one of the hosts within the vCenter server
 2. Power down the VCH appliance
 3. vMotion the VCH appliance to a new host
@@ -25,8 +25,8 @@ This test requires that a vCenter server is running and available
 12. vMotion the VCH appliance to a new host
 13. Complete the life cycle of the containers created in Step 11, including getting docker logs and re-attaching to containers that are running
 
-#Expected Outcome:
+# Expected Outcome:
 In each scenario, the VCH appliance should continue to work as expected after being vMotioned and all docker commands should return without error
 
-#Possible Problems:
-None
+# Possible Problems:
+None

tests/manual-test-cases/Group13-vMotion/13-2-vMotion-Container.md

@@ -1,23 +1,23 @@
 Test 13-2 vMotion Container
 =======
 
-#Purpose:
+# Purpose:
 To verify the VCH appliance continues to function properly after some or all of it's related containers are vMotioned
 
-#References:
+# References:
 [1- vMotion A Powered On Virtual Machine](http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.dcadmin.doc_41/vsp_dc_admin_guide/migrating_virtual_machines/t_migrate_a_powered-on_virtual_machine_with_vmotion.html)
 
-#Environment:
+# Environment:
 This test requires that a vCenter server is running and available
 
-#Test Steps:
+# Test Steps:
 1. Install a new VCH appliance onto one of the hosts within the vCenter server
 2. Create several containers on the new VCH appliance that are in the following states: created but not started, started and running, started and stopped, stopped after running and being attached to, running after being attached to but currently not attached to, running and currently attached to
 3. vMotion each of the containers to a new host within the vCenter server
 4. Complete the life cycle of the containers created in Step 2, including getting docker logs and re-attaching to containers that are running
 
-#Expected Outcome:
+# Expected Outcome:
 In each scenario, the VCH appliance should continue to work as expected after being vMotioned and all docker commands should return without error
 
-#Possible Problems:
-None
+# Possible Problems:
+None