diff --git a/docs/validate_pods.md b/docs/validate_pods.md
index 762f1f7..8332dde 100644
--- a/docs/validate_pods.md
+++ b/docs/validate_pods.md
@@ -59,5 +59,36 @@
 
 ### Data Plane Tests
 
-For CORD 6.0 release, data plane tests are executed manually on the
-POD using OLT/ONU.
+Data plane tests include validations of both top-down and zero-touch approaches as well as workflow validations. Follow the guide above to edit the properties file before running the tests.
+
+**Validating top-down and zero-touch approaches**
+
+`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
+```
+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
+```
+
+**Validating AT&T workflow**
+
+Test scripts and input data for validating AT&T workflow are under `cord-tester/src/test/cord-api/Tests/WorkflowValidations`. The same test script e.g. `ATT_Test001.robot` works with different POD setups. Instead of hardcoding the POD specific variables in the test script, it relies on a separated configuration file which describes POD setup. To create a configuratino file for your POD please take a look at [this example](https://github.com/opencord/pod-configs/blob/master/deployment-configs/flex-pod1-olt.yaml).
+
+Input data are stored under `cord-tester/src/test/cord-api/Tests/WorkflowValidations/data/`. Please create a new folder with the name of your POD and copy and data files from e.g. `flex-pod1-olt` folder and edit them with the correct values on your POD.
+
+Also make sure that the variables in the test script (e.g. `ATT_Test001.robot`) are correct. Specifically, verify that `${POD_NAME}` is the same as the folder name you created above, and `${KUBERNETES_CONF}` is pointing to your Kubernetes configuration file.
+
+After updating all these POD specific values, execute the following commands to trigger the test
+
+```bash
+cd cord-tester/src/test/cord-api/Tests/WorkflowValidations
+pybot -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).