Triggered by merges in policy/engine, policy/drools-pdp, and policy/drools-applications
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Lab |
|---|---|---|---|---|---|
1 | Perform healthcheck for the Policy components using Healthcheck API
|
| API – healthcheck Method - GET Endpoint: http://<host>:6969/policy/pdpd/v1/engine/healthcheck | All the policy components should return health status as “true” | CSIT/External Lab |
|
|
|
(legacy API) |
| CSIT |
3 | Create config Policy for the following use cases
| Policy components up and running | API – CreateConfig Method – PUT Endpoint: https://<host>:8081/pdp/api/createPolicy (legacy API) | Config Policy should be created in Policy Engine (PAP) | CSIT |
4 | Push Config policy to the PDP Engines for the following use cases
| Policy components up and running | API - pushPolicy Method - PUT Endpoint: https:// <host>:8081/pdp/api/pushPolicy (legacy API) | Config Policy should be pushed to the PDP group | CSIT |
5 | Create Operational policy for the following use cases
| Policy components up and running | API - createPolicy Method – PUT Endpoint: https://<host>:8081/pdp/api/createPolicy (legacy API) | Operational Policy should be created in Policy Engine (PAP) | CSIT |
6 | Push operational Policy to the PDP Engines for each use case
| Policy components up and running | API - pushPolicy Method - PUT Endpoint: https:// <host>:8081/pdp/api/pushPolicy (legacy API) | Operational Policy should be pushed to the PDP group | CSIT |
7 | Retrieve the configs for the following use cases
| Policy components up and running | API – getConfig Method – POST Endpoint: https://<host>:8081/pdp/api/getConfig (legacy API) | Both Config and Operational Policies configured for each use case should be retrieved successfully | CSIT |
Triggered by merges in policy/distribution
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Lab |
|---|---|---|---|---|---|
1 | Perform healthcheck of the component | Policy distribution docker image is available | API – healthcheck Method - GET Endpoint: https://<host>:6969/policy/distribution/v1/healthcheck | The component should return health status as “true” | CSIT/External Lab |
| 2 | Query component for statistics | Policy distribution docker image is available | API - statistics Method - GET Endpoint: https://<host>:6969/policy/distribution/v1/statistics | The component should return the current statistics of the component. | CSIT |
Triggered by merges in policy/pap
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Lab |
|---|---|---|---|---|---|
| 1 | Perform healthcheck of the component | PAP docker image is available | API – healthcheck Method - GET Endpoint: https://<host>:6969/policy/pap/v1/healthcheck | The component should return health status as “true” | CSIT/External Lab |
| 2 | Query component for statistics | PAP docker image is available | API - statistics Method - GET Endpoint: https://<host>:6969/policy/pap/v1/statistics | The component should return the current statistics of the component. | CSIT |
| 3 | Query pdp group information | PAP docker image is available | API - pdps Method - GET Endpoint: https:{url}:{port}/pap/v1/pdps | The component should return the list of PDP groups and subgroups together with the policies that are deployed on each PDP group and subgroup. | CSIT |
| 4 | Create PDP group & subgroup | PAP docker image is available | API - pdps Method - POST Endpoint: https:{url}:{port}/pap/v1/pdps | The component should create the relevant PDP group & subgroup in the database and return with operation success message/code. | CSIT |
| 5 | Deploy policy to PDP group & subgroup | PAP docker image is available PAP docker image is available | API - pdps Method - POST Endpoint: https:{url}:{port}/pap/v1/pdps | The component should map the relevant policies with the corresponding PDP group & subgroup in database. Deploy the policy in relevant PDP and return with operation success message/code. | CSIT |
| 6 | Query pdp group statistics | PAP docker image is available PDP docker image is available | API - pdps Method - GET Endpoint: https:{url}:{port}/pap/v1/pdps/statistics | The PAP component must return the statistics for PDP groups, subgroups and individual PDPs. | CSIT |
| 7 | Delete PDP group & subgroup | PAP docker image is available PDP docker image is available | API - pdps Method - DELETE Endpoint: https:{url}:{port}/pap/v1/pdps?name=<group_name>&version=<version> | The component should delete the relevant PDP group & subgroup from database and kill the corresponding PDP instances (running as kubernetes pods). Finally, return with operation success message/code. | CSIT |
Triggered by merges in policy/drools-pdp (NOT FINISHED)
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Labs |
|---|---|---|---|---|---|
| 1 | Health Check | Drools-PDP docker image available | |||
| 2 | Statistics | Drools-PDP docker image available | |||
...
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Labs |
|---|---|---|---|---|---|
1 | Perform healthcheck for the Policy Apex PDP |
| API – healthcheck Method - GET Endpoint: http://<host>:8081/healthcheck(?) | The Apex PDP should return health status as “true” | |
2 | Create Operational policies for the following use cases
| Policy components up and running | (Will be added once API page approved) (Current integration tests for REST client moved to CSIT) | Operational Policy should be created in Policy Engine Policy should fire and return a result | |
| 3 | Query component for statistics | Policy PSSD docker image available | API - Statistics (details TBD) | Statistics on execution are available and sane. |
...
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT External Labs |
|---|---|---|---|---|---|
1 | Perform healthcheck for policy design API service |
| API – healthcheck Method - GET Endpoint: http://<host>:6969/api/v1/healthcheck | The Policy API should return health status as “true” | |
| 2 | Retrieve statistics of policy design API invocation |
| API – statistics Method - GET Endpoint: http://<host>:6969/api/v1/statistics | The Policy API should return API invocation statistics report with code set to "200" | |
| 3 | Retrive pre-loaded generic policy types |
| API – policytypes Method - GET Endpoint: http://<host>:6969/api/v1/policytypes | The Policy API should return a list of pre-loaded generic policy types | |
| 4 | Retrive Monitoring related policy types |
| API – policytypes/onap.policies.Monitoring Method - GET Endpoint: http://<host>:6969/api/v1/policytypes/onap.policies.Monitoring | The Policy API should return a list of onap.policies.Monitoring and derived onap.policies.Monitoring.cdap.tca.hi.lo.app policy types | |
| 5 | Create a new TCA policy type for DCAE TCA microservice |
| API – policytypes Method - POST Endpoint: http://<host>:6969/api/v1/policytypes | The Policy API should return code 200 and message "A new policy type has been successfully created." | |
| 6 | Retrieve policies that have been created |
| API – policies Method - GET Endpoint: http://<host>:6969/api/v1/policies | The Policy API should return a list of policies that have been created, including onap.scaleout.tca | |
| 7 | Create a new Monitoring TCA policy |
| API – policies Method - POST Endpoint: http://<host>:6969/api/v1/policies | The Policy API should return code 200 and message "A new policy has been successfully created." |
...