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: https://<host>:6969/policy/pdpd/v1/engine/healthcheck (legacy policy system healthcheck with new REST API format) | All the policy components should return health status as “true” | CSIT - DONE External Lab - DONE |
2 | Import/Load Use case template for the following use cases (VoLTE, vCPE, vFW, vDNS) | Policy components should be up and running | API – policyEngineImport Method – POST Endpoint: https://<host>:8081/pdp/policyEngineImport (legacy API) | Policy service models should be imported for the specified use cases. We should be able to create policy from here. | 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 - DONE |
4 | Create SDNC naming policies | Policy components up and running | Naming policy should be created in Policy Engine (PAP) | CSIT - DONE External Lab - Done | |
5 | Create Decision Guard Policy | Guard policy should be created in Policy Engine (PAP) | CSIT -DONE External Lab - Done | ||
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 - DONE |
Push Decision Guard Policy | CSIT External Lab - DONE | ||||
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 - DONE |
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 - DONE |
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 - DONE |
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 - DONE External Lab - DONE |
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 |
...
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 - DONE External Lab - DONE |
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 - DONE External Lab - DONE |
3 | Query pdp group information | PAP docker image is available | API - pdps Method - GET Endpoint: https:{url}:{port}/policy/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}/policy/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}/policy/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}/policy/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}/policy/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 |
...
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Labs |
---|---|---|---|---|---|
1 | Alive | Verify that base barebone PDP-D comes alive | API – telemetry Method - GET Endpoint: https://<host>:69699696/policy/pdpd/v1/engine | Verify alive field | CSIT |
2 (stretch) | Dynamic Controller Creation | Verify dynamic addition of a PDP-D controller | API – telemetry Method - GET Endpoint: https://<host>:69699696/policy/pdpd/v1/controllers/<controller> | Verify that the dynamically create controller is alive. | CSIT |
3 (stretch) | Dynamic Controller Traffic | Verify that PDP-D can process traffic for the controller created in step-2. | API – telemetry Method - GET Endpoint: https://<host>:69699696/policy/pdpd/v1/controllers/<controller>/drools | Verify that the events structure contains input and expected output messages. | CSIT |
...
Triggered by merges in policy/apex-pdp
Test Case Id | Description | Pre-conditions | Test Steps | Expected Results | CSIT/External Labs |
---|---|---|---|---|---|
1 | Perform healthcheck of the component | Apex PDP docker image is available | API – healthcheck Method - GET Endpoint: https://<host>:6969/policy/apex-pdp/v1/healthcheck | The component should return health status as “true” | CSIT - DONE External Lab |
2 | Query component for statistics | Apex PDP docker image is available | API - statistics Method - GET Endpoint: https://<host>:6969/policy/apex-pdp/v1/statistics | The component should return the current statistics of the component. | CSIT |
3 | 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 apex-pdp | CSIT |
Triggered by merges in policy/api
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/policy/api/v1/healthcheck | The Policy API should return health status as “true” | CSIT - DONE External Lab - DONE |
2 | Retrieve statistics of policy design API invocation |
| API – statistics Method - GET Endpoint: http://<host>:6969/policy/api/v1/statistics | The Policy API should return API invocation statistics report with code set to "200" | CSIT - DONE External Lab - DONE |
3 | Retrieve pre-loaded generic policy types |
| API – policytypes Method - GET Endpoint: http://<host>:6969/policy/api/v1/policytypes | The Policy API should return a list of pre-loaded generic policy types | CSIT |
4 | Create a new TCA policy type for DCAE TCA microservice |
| API – policytypes Method - POST Endpoint: http://<host>:6969/policy/api/v1/policytypes | The Policy API should return code 201 and message "A new policy type has been successfully created." | CSIT |
5 | Retrieve Monitoring related policy types |
| API – policytypes/onap.policies.Monitoring Method - GET Endpoint: http://<host>:6969/policy/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 | CSIT |
6 | Create a new Monitoring TCA policy |
| API – policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies Method - POST Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies | The Policy API should return code 201 and message "A new policy has been successfully created." | CSIT |
7 | Retrieve all policies created for a specific policy type |
| API – policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies Method - GET Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies | The Policy API should return a list of policies that have been created for onap.policies.Monitoring.cdap.tca.hi.lo.app version 1.0.0 policy type, including onap.scaleout.tca | CSIT |
8 | Delete all versions of a policy |
| API – policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies/onap.scaleout.tca Method - DELETE Endpoint: http://<host>:6969/policy/api/v1/policytypes/onap.policies.Monitoring.cdap.tca.hi.lo.app/versions/1.0.0/policies/onap.scaleout.tca | The Policy API should delete all versions of onap.scaleout.tca policy and return code 200 | CSIT |
...