Add documentation for CL participants smoke testing

[policy/parent.git] / docs / development / devtools / devtools.rst

diff --git a/docs/development/devtools/devtools.rst b/docs/development/devtools/devtools.rst
index 2351a32..cc973ed 100644 (file)
--- a/docs/development/devtools/devtools.rst
+++ b/docs/development/devtools/devtools.rst
@@ -233,7 +233,7 @@ Developing and Debugging each Policy Component
 Running a MariaDb Instance
 ++++++++++++++++++++++++++
 
-The Policy Framework requires a MariaDb instance running. The easiest way to do this is to run a docker image locally. 
+The Policy Framework requires a MariaDb instance running. The easiest way to do this is to run a docker image locally.
 
 One example on how to do this is to use the scripts used by the policy/api S3P tests.
 
@@ -276,6 +276,11 @@ familiar with the Policy Framework components and test any local changes.
 .. toctree::
    :maxdepth: 1
 
+   policy-gui-controlloop-smoke.rst
+
+   db-migrator-smoke.rst
+
+   cl-participants-smoke.rst
 ..
    api-smoke.rst
 
@@ -297,6 +302,9 @@ familiar with the Policy Framework components and test any local changes.
 ..
    clamp-smoke.rst
 
+..
+   clamp-cl-participant-protocol-smoke.rst
+
 Running the Stability/Performance Tests
 ***************************************
 
@@ -315,7 +323,7 @@ familiar with the Policy Framework components and test any local changes.
    clamp-s3p.rst
 
 Running the Pairwise Tests
-***********************
+**************************
 
 The following links contain instructions on how to run the pairwise tests. These may be helpful to developers check that
 the Policy Framework works in a full ONAP deployment.