Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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>:<port>/healthcheck

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

2

Create config Policy for the following use cases

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

Policy components up and   running

API – CreateConfig

Method – PUT

Endpoint:

https://<host>:<port>/PyPDPServer/createConfig

Config Policy should be created in Policy Engine

3

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>:<port>/PyPDPServer/pushPolicy

Config Policy should be pushed to the PDP group

4

Create Operational policy for the following use cases  

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

Policy components up and running

API - createPolicy  

Method – PUT

Endpoint:

https://<host>:<port>/PyPDPServer/createPolicy

Operational Policy should be created in Policy Engine

5

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>:<port>/PyPDPServer/pushPolicy

Operational Policy should be pushed to the PDP group

6

Retrieve the configs for the following use cases

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE

Policy components up and running

API – getConfig

Method – POST

Endpoint:

https://<host>:<port>/PyPDPServer/getConfig

Policy configuration

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

7

Import/Load Use case template for the following use cases (VoLTE,   vCPE, vFW, vDNS)

 

 

 

8

Load the Drools Controller Configurations


 

 

9

Simulate DCAE Control loop event for each use case with higher  or lower threshold values

  •   VoLTE
  •   vFW
  •   vDNS
  •   vCPE
  • Policy components up and running
  • Simulator should be available

Invoke the Simulator API to trigger a DCAE control loop event

DCAE event should be triggered to Policy for each use case depending on the threshold configured in Policy

10

Simulate APPC Response for Use Case VFW & vCPE

  • Policy components up and running
  • Simulator should be available

Invoke APPC simulator API with Policy data or Trigger a DCAE   control loop event for vFW/vCPE

Valid Response from AppC Simulator API

11

Simulate VF-C Response for Use Case VOLTE

  • Policy components up and running
  • Simulator should be available

Invoke VF-C simulator API with Policy data or Trigger a DCAE   control loop event for VOLTE

Valid Response from VF-C Simulator API

12

Simulate SO Response for VDNS

  • Policy components up and running
  • Simulator should be available

Invoke SO simulator API with Policy data or Trigger a DCAE   control loop event for vDNS

Valid Response from SO Simulator API

13

Simulate A&AI Response for VDNS

  • Policy components up and running
  • Simulator should be available

Invoke A&AI simulator API with Policy data or Trigger a DCAE   control loop event for vDNS

Valid Response from A&AI Simulator API