Updates to System Test Guide
Change-Id: Ide25c95f7f719d9829dd6b10081866f492062923
diff --git a/docs/images/SEBA-QA-Jenkins.png b/docs/images/SEBA-QA-Jenkins.png
new file mode 100644
index 0000000..1d1b78b
--- /dev/null
+++ b/docs/images/SEBA-QA-Jenkins.png
Binary files differ
diff --git a/docs/images/flex-qa-pod.png b/docs/images/flex-qa-pod.png
new file mode 100644
index 0000000..a7322d1
--- /dev/null
+++ b/docs/images/flex-qa-pod.png
Binary files differ
diff --git a/docs/qa_testenv.md b/docs/qa_testenv.md
index 29f3aa0..16462fb 100644
--- a/docs/qa_testenv.md
+++ b/docs/qa_testenv.md
@@ -18,7 +18,7 @@
The following diagram shows how the test servers are interconnected
-
+
* To view results from recent runs of the jenkins jobs, please view the
[Jenkins dashboard](https://jenkins.opencord.org/)
diff --git a/docs/qa_testsetup.md b/docs/qa_testsetup.md
index 1d9c6cf..d5a044a 100644
--- a/docs/qa_testsetup.md
+++ b/docs/qa_testsetup.md
@@ -35,7 +35,7 @@
```bash
cd cord-tester/src/test/robot/
- pybot SanityK8POD.robot
+ robot SanityK8POD.robot
```
### Executing Control Plane Tests
@@ -60,7 +60,5 @@
```bash
cd cord-tester/src/test/cord-api/Tests/
- pybot <testcase.txt>
+ robot <testcase.txt>
```
- For more detailed explanations of the cord-tester options please see [Running
- Tests](running.md).
diff --git a/docs/validate_pods.md b/docs/validate_pods.md
index 8332dde..6d89e09 100644
--- a/docs/validate_pods.md
+++ b/docs/validate_pods.md
@@ -24,7 +24,7 @@
```bash
cd cord-tester/src/test/diag
-pybot SanityK8Pod.robot
+robot SanityK8Pod.robot
```
## Functional Tests
@@ -53,8 +53,8 @@
```bash
cd cord-tester/src/test/cord-api/Tests/
-pybot VOLTDevice_Test.txt
-pybot RCORDLite_E2ETest.txt
+robot VOLTDevice_Test.txt
+robot RCORDLite_E2ETest.txt
```
### Data Plane Tests
@@ -66,14 +66,14 @@
`Subscriber_StatusChecks.txt` validates subscriber status and end-to-end ping. Execute the following commands to run the test.
```bash
cd cord-tester/src/test/cord-api/Tests/
-pybot -v init_state:disabled -v INITIAL_STATUS:FAIL -v ENABLE_STATUS:PASS -e zerotouch Subscriber_StatusChecks.txt
+robot -v init_state:disabled -v INITIAL_STATUS:FAIL -v ENABLE_STATUS:PASS -e zerotouch Subscriber_StatusChecks.txt
```
Remember to change the values (ip, gateway, username, password, etc.) in the `Variables` section of the script to point the test to the source and destination hosts in your environment before running it.
Similarly, run the follownig commands to validate zero-touch approach. Note that the arguments passed to the test script are different from the top-down approach.
```bash
cd cord-tester/src/test/cord-api/Tests/
-pybot -v init_state:awaiting-auth -v INITIAL_STATUS:FAIL -v ENABLE_STATUS:FAIL -v MACIP_STATUS:PASS Subscriber_StatusChecks.txt
+robot -v init_state:awaiting-auth -v INITIAL_STATUS:FAIL -v ENABLE_STATUS:FAIL -v MACIP_STATUS:PASS Subscriber_StatusChecks.txt
```
**Validating AT&T workflow**
@@ -88,7 +88,7 @@
```bash
cd cord-tester/src/test/cord-api/Tests/WorkflowValidations
-pybot -V PATH_TO_YOUR_POD_CONFIGURATION_FILE ATT_Test001.robot
+robot -V PATH_TO_YOUR_POD_CONFIGURATION_FILE ATT_Test001.robot
```
Note that `PATH_TO_YOUR_POD_CONFIGURATION_FILE` should point to the yaml file that describes your POD setup (see above).
