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

Compare with Current View Page History

« Previous Version 4 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>:8081/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

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and   running

API – CreateConfig

Method – PUT

Endpoint:

https://<host>:8081/Pdp/createPolicy

Config Policy should be created in Policy Engine (PAP)

4

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

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and running

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/Pdp/pushPolicy

Config Policy should be pushed to the PDP group

5

Create Operational policy for the following use cases  

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:8081/Pdp/createPolicy

Operational Policy should be created in Policy Engine (PAP)

6

Push operational Policy to the PDP Engines for each use case

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

 Policy components up and running

API - pushPolicy  

Method - PUT

Endpoint:

https:// <host>:8081/Pdp/pushPolicy

Operational Policy should be pushed to the PDP group

7

Retrieve the configs for the following use cases

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

Policy components up and running

API – getConfig

Method – POST

Endpoint:

https://<host>:8081/Pdp/getConfig

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

Triggered by merges in policy/distribution (NOT FINISHED)

Test Case Id

Description

Pre-conditions

Test Steps

Expected Results

1

Perform healthcheck for the Policy SDC Service

Distribution application


  • Policy PSSD docker image available

API – healthcheck

Method - GET

Endpoint: http://<host>:8081/health(?)

The Policy PSSD should return health status as “true”






Triggered by merges in policy/apex-pdp (Stretch - DONE)

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”






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