You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Triggered by merges in policy/engine, policy/drools-pdp, and policy/drools-applications

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1

Perform   healthcheck for the Policy components using Healthcheck API

  •   Drools PDP
  •   XACML PDP
  •   PAP
  •   BRMSGateway
  • Policy docker image ready and policy   components (Drools, XACML, PAP, BRMS Gateway) should be up and running
  • Server and authentication details should   be configured at  $POLICY_HOME/config/feature-healthcheck.properties

API – healthcheck

Method - GET

Endpoint: http://<host>:6969/healthcheck

All the policy components should return health status as “true”

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

Policy service models should be imported for the specified use   cases. We should be able to create policy from here.

3

Create config Policy for the following use cases

  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and   running

API – CreateConfig

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

Config Policy should be created in Policy Engine (PAP)

4

Push Config policy to the PDP Engines for the following use   cases

  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and running

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

Config Policy should be pushed to the PDP group

5

Create Operational policy for the following use cases  

  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/pdp/api/createPolicy

Operational Policy should be created in Policy Engine (PAP)

6

Push operational Policy to the PDP Engines for each use case

  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and running

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/pdp/api/pushPolicy

Operational Policy should be pushed to the PDP group

7

Retrieve the configs for the following use cases

  •   vFW
  •   vDNS
  •   vCPE

Policy components up and running

API – getConfig

Method – POST

Endpoint: https://<host>:8081/pdp/api/getConfig

Both Config and Operational Policies configured for each use   case should be retrieved successfully

Triggered by merges in policy/distribution

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

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”

2Query component for statisticsPolicy 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.

Triggered by merges in policy/pap (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1Perform healthcheck of the componentPAP docker image is available

API – healthcheck

Method - GET

Endpoint: https://<host>:6969/policy/pap/v1/healthcheck

The component should return health status as “true”
2Query component for statisticsPAP 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.
3Query pdp group informationPAP 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.
4Create PDP group & subgroupPAP 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.
5Deploy 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.
6Query 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.
7Delete 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.


Triggered by merges in policy/drools-pdp (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1Health CheckDrools-PDP docker image available

2StatisticsDrools-PDP docker image available











Triggered by merges in policy/xacml-pdp (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

CSIT/External Lab
1Health CheckXacml-PDP docker image availableGETShould pass Health checkCSIT/External Lab
2StatisticsXacml-PDP docker image availableGETShould list 0 policies loaded, 0 decisionsCSIT
3Deploy PolicyXacml-PDP and PAP docker images availablePOSTSuccess deploy of policy to XACML PDPCSIT/External Lab (stretch)
4StatisticsXacml-PDP and PAP docker images availableGETStatistics should list 1 policy loadedCSIT
5Decision API

Xacml-PDP docker image available

POSTCorrect DecisionCSIT/External Lab (stretch)
6StatisticsXacml-PDP docker image availableGETStatistics should increment decision countCSIT
7Undeploy PolicyXacml-PDP and PAP docker images availablePOSTSuccess undeploy of policyCSIT
8StatisticsXacml-PDP docker image availableGETShould list 0 policies loaded, 1 decisionCSIT


Triggered by merges in policy/apex-pdp (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1

Perform healthcheck for the Policy Apex PDP


  • Apex PDP docker image available

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  

  • SampleDomain
  • BBS (if this is not a POC)

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

3Query component for statisticsPolicy PSSD docker image availableAPI - Statistics
(details TBD)		Statistics on execution are available and sane.

Triggered by merges in policy/api (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1

Perform healthcheck for policy design API service


  • Policy API docker image available

API – healthcheck

Method - GET

Endpoint: http://<host>:6969/api/v1/healthcheck

The Policy API should return health status as “true”

2Retrieve statistics of policy design API invocation
  • Policy API docker image available

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"
3Retrive pre-loaded generic policy types
  • Policy API docker image available

API – policytypes

Method - GET

Endpoint: http://<host>:6969/api/v1/policytypes

The Policy API should return a list of pre-loaded generic policy types
4Retrive Monitoring related policy types
  • Policy API docker image available
  • DCAE TCA ms policy type is created

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
5Create a new TCA policy type for DCAE TCA microservice
  • Policy API docker image available
  • DCAE TCA ms policy type is not created yet

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."
6Retrieve policies that have been created
  • Policy API docker image available
  • onap.scaleout.tca policy has 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
7Create a new Monitoring TCA policy
  • Policy API docker image available
  • onap.scaleout.tca policy has not been created

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."
  • No labels