From d6aca81699ec0937e4ef971315180326ee446cd1 Mon Sep 17 00:00:00 2001 From: jhh Date: Tue, 26 Apr 2022 12:34:49 -0500 Subject: smoke tests doc for xacml and drools Issue-ID: POLICY-3720 Issue-ID: POLICY-3721 Signed-off-by: jhh Change-Id: I48651d5633d15289efc827c8dcf5bad8671fba4f --- docs/development/devtools/drools-smoke.rst | 62 ++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 docs/development/devtools/drools-smoke.rst (limited to 'docs/development/devtools/drools-smoke.rst') diff --git a/docs/development/devtools/drools-smoke.rst b/docs/development/devtools/drools-smoke.rst new file mode 100644 index 00000000..07c812c4 --- /dev/null +++ b/docs/development/devtools/drools-smoke.rst @@ -0,0 +1,62 @@ +.. 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 Drools PDP and Applications Smoke Test +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The policy-drools-pdp smoke testing can be executed against a kubernetes based ONAP installation, +and/or a docker-compose set up similar to the one executed by CSIT tests. + +General Setup +************* + +ONAP OOM kubernetes +------------------- + +For installation instructions, please refer to the following documentation: + +`OOM Quick Start Guide `_ + +At a minimum policy needs the following components installed: + +- onap base charts +- AAF for certificate generation +- DMaaP message-router for communication among policy components. + +AAI, SO and other components can be simulated by installing the simulator charts: + +`Policy Simulator Helm Chart `_ + +docker-compose based +-------------------- + +A smaller testing environment can be put together by replicating the CSIT test environment: + +`Policy CSIT Test infrastructure `_ + +Testing procedures +****************** + +The smoke tests should be focused on verifying the proper workings of drools +and dependent components. The following scenarios should be considered: + +- PDP-D registration with PAP. +- PDP-D restarts and re-registration with PAP. +- Proper workings of telemetry tool. +- Exploration of correct PDP-D states with the telemetry tool. +- Statistics and prometheus metrics. +- Verify correct states of API, PAP, and controllers using the PDP-D healthchecks. +- Verify distributed locking capability and proper use of the database. +- Verify vCPE, vDNS, and vFirewall use cases and recorded metrics. + +The following testsuites contain everything necessary for the previous verifications: + +- `CSIT Robot framework `_ +- `JMeter S3P `_ + -- cgit 1.2.3-korg