Restructure of devtools folder for smoke tests

Move smoke tests docs to smoke folder

Issue-ID: POLICY-4627
Change-Id: Ica496db009c5e15b531fc0d6c3d93596f0425b28
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>

1 files changed, 47 insertions, 0 deletions

diff --git a/docs/development/devtools/smoke/api-smoke.rst b/docs/development/devtools/smoke/api-smoke.rst
new file mode 100644
index 00000000..8230f33b
--- /dev/null
+++ b/docs/development/devtools/smoke/api-smoke.rst
@@ -0,0 +1,47 @@
+.. This work is licensed under a
+.. Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _policy-api-smoke-testing-label:
+
+.. toctree::
+   :maxdepth: 2
+
+Policy API Smoke Test
+~~~~~~~~~~~~~~~~~~~~~
+
+The policy-api smoke testing is executed against a default ONAP installation as per OOM charts.
+This test verifies the execution of all the REST api's exposed by the component to make sure the contract works as expected.
+
+General Setup
+*************
+
+The kubernetes installation will allocate all onap components across multiple worker node VMs.
+The normal worker VM hosting onap components has the following spec:
+
+- 16GB RAM
+- 8 VCPU
+- 160GB Ephemeral Disk
+
+
+The ONAP components used during the smoke tests are:
+
+- Policy API to perform CRUD of policies.
+- Policy DB to store the policies.
+
+
+Testing procedure
+*****************
+
+The test set is focused on the following use cases:
+
+- Execute all the REST api's exposed by policy-api component.
+
+Execute policy-api testing
+--------------------------
+Download & execute the steps in postman collection for verifying policy-api component.
+The steps need to be performed sequentially one after another. And no input is required from user.
+
+`Policy Framework Lifecycle API <https://github.com/onap/policy-api/blob/master/postman/lifecycle-api-collection.json>`_
+
+Make sure to execute the delete steps in order to clean the setup after testing.