Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 8 Next »

Integration Testing

Use case StepComponent(s)FunctionalityTest caseImpacted APIStatus
5PCI-Handler MS, OOFRequest for PCI optimization for network region.
PCI-Handler MS invokes OOF for pre-defined workflow for PCI Optimization via REST API.This call includes data for the cell and the network reqion involved.

Ensure that PCI-Handler-MS applies configuration policies, processes configuration changes in steps 4a,4b, and sends a message to OO

(Pre-requisite is step 2 is tested)

<API details>Not tested
6OOF, PolicyFetch PCI optimization policies
OOF fetches policies that specify how OOF will execute PCI optimization in response to PCI request for optimization		Ensure that OOF can fetch optimization policies from Policy, and applies it to invoke the appropriate solver module<Policy API details>Not tested
7OOF, SDN-CFetch Config data for cells in the region.
OOF fetches data for cells in network region from SDN-C		Ensure that OOF can query SDN-C to get required data (e.g. cellids, nbr_list, pci, lat/lon) from SDN-C Config DB<Config DB API details>Not tested
9PCI-Handler MS, PolicyRecommended PCI configuration.
PCI-Handler-MS provides PCI recommendation to Policy		Ensure that PCI-Handler-MS sends a message to Policy with recommendation for new PCI values for set of cells, along with reason for oprimization computation (RAN config change)
Not tested
10Policy, SDN-CPCI Configuration decisions
Policy sends message to SDN-C with instruction for configuration changes		Ensure that Policy applies operational policies to PCI change recommendation, and if appropriate, sends a message to SDN-C with instruction to change PCI value to set of cells
Not tested






Test Case ID

POLICY_OOF_PAIRWISE_001

Test Case Name

Configuration of OOF


Description

Test if the OOF is onboarded and configuration policies are fetched and loaded correctly (Step 1c of flow)

Release

Casablanca

Pre-conditions

(a) Policy module is onboarded.

(b) Config policies related to OOF are provisioned properly in Policy module.

Testing Steps

Steps

Expected Result

  1. Bring up the OOF using the installation steps.
  2. Check the OOF database to see the contents of the OOF config policy for PCI optimization use case.
  1. OOF comes online and the database and local datastructures for PCI optimization use case are initialized correctly.
  2. Config-policy is correctly fetched and stored in the OOF DB.
    Sample config policy contents are given below:
    ALGO_CATEGORY:OOF-PCI-OPTIMIZATION
    PCI_OPTMIZATION_ALGO_NAME:OOF-PCI-OPTIMIZATION-LEVEL1
    PCI_OPTIMIZATION_NW_CONSTRAINT:MAX5PCICHANGESONLY
    PCI_OPTIMIZATION_PRIORITY: 2
    PCI_OPTIMIZATION_TIME_CONSTRAINT:NONE

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

POLICY_PCIMS_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 (Step 1b of flow)

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 PCI-MS database to see the contents of the PCI-MS config policy.
  1. PCI-MS comes online and the database and local datastructures (e.g., thread pool) are initialized correctly.
  2. Config-policy is correctly fetched and stored in the PCI-MS DB.
    Sample config policy contents are given below:
    PCI_NEIGHBOR_CHANGE_CLUSTER_TIMEOUT_IN_SECS:60
    PCI_MODCONFIG_POLICY_NAME:ControlLoop-vPCI-fb41f388-a5f2-11e8-98d0-529269fb1459 PCI_OPTMIZATION_ALGO_CATEGORY_IN_OOF:OOF-PCI-OPTIMIZATION
    PCI_SDNR_TARGET_NAME:SDNR

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

SDNR_RAN_PAIRWISE_001

Test Case Name

Connecting SDN-R with RAN (netconf servers)

Description

Establish connection between SDN-R and RAN

Release

Casablanca

Pre-conditions

(a) SDN-R is up and running

(b) RAN initialization file is available

Testing Steps

Steps

Expected Result

  1. Bring up the RAN-Simulator using the installation steps.
  2. Observe the connection status between SDN-R and netconf server(s)
  1. RAN-Simulator is successfully instantiated. GUI also shows the appropriate topology view.
  2. SDN-R and netconf servers are connected (RAN-Simulator sends a mount request (REST) for each netconf server.


Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

SDNR_RAN_PAIRWISE_002

Test Case Name

Receiving neighbor list change notification from RAN

Description

Receive a neighbor list change notification from RAN and act upon it by sending a DMaaP notification to PCI-MS (after storing relevant info in Config DB).

Release

Casablanca

Pre-conditions

(a) SDN-R is up and running

(b) RAN is connected to SDN-R, GUI shows RAN topology view properly

Testing Steps

Steps

Expected Result


  1. RA.


Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

SDNR_PCIMS_PAIRWISE_001

Test Case Name

Handle neighbor list change notification from SDN-R


Description


Release

Casablanca

Pre-conditions

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


Testing Steps

Steps

Expected Result

  1. P
  1. AP

    (b) getPnfName

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

SDNR_PCIMS_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 using the RAN initialization file.

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
  1. API query is successful and results match with DB contents.
    Sample API query and results:
    (a) getNbrList

    (b) getPnfName

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

OOF_PCI_PAIRWISE_003


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

  • No labels