summaryrefslogtreecommitdiffstats
path: root/docs/development/devtools/smoke/api-smoke.rst
blob: 8230f33b3e25e71c03ae258d0228cd3f660fe461 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
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.