Versions Compared

Version Old Version 5 New Version 6
Changes made by

Swaminathan Seetharaman

Swaminathan Seetharaman

Saved on

Key

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

...

Test Case ID

OOF_PCI_PAIRWISE_001


Test Case Name

Configuration of PCI-MS


Description

Test if the PCI-MS is onboarded and configuration policies are fetched and loaded correctly.

Release

Casablanca

Pre-conditions

(a) Policy module is onboarded.

(b) Config policies related to PCI-MS are provisioned properly in Policy module.

Testing Steps

Steps

Expected Result

  1. Bring up the PCI-MS using the intallation steps.
  2. Check the DB to see the contents of the PCI-MS config policy.
  1. Config-policy is correctly fetched and stored in the PCI-MS DB.


Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case ID

OOF_PCI_PAIRWISE_002


Test Case Name

Config DB API access

Description

Test the working of Config DB APIs

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network.

Testing Steps

Steps

Expected Result

  1. PCI-MS does a query to the configDB using the APIs to get:
    (a) Neighbor list
    (b) pnf-name
    Example query:
  2. OOF does a query to the configDB to get:
    (a) Complete list of cells in the network
    Example query:
  1. API query is successful and results match with DB contents.
  2. API query is successful and results match with DB contents.


Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case ID

OOF_PCI_PAIRWISE_001003


Test Case Name

Request for PCI optimization

Description

Request for PCI optimization algorithm to be executed by OOF to address PCI collision/confusion

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) (SDN-R) Config DB should be populated with the details of the cells in the network.

Testing Steps

Steps

Expected Result

  1. Send a DMaaP notification to PCI-MS with neighbor list change information.
  2. PCI-MS determines the collisions/confusions (neighbor of neighbor info is obtained by invoking REST call to Config DB).

          





Conclusion (Pass /Fail)


Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine