Pair-wise testing

S.No.	Test case ID	Components

Integration Testing

Use case Step	Component(s)	Functionality	Test case	Impacted APIStatus	Status
5	PCI-Handler MS, OOF	Request 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
6	OOF, Policy	Fetch 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
7	OOF, SDN-C	Fetch 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
9	PCI-Handler MS, Policy	Recommended 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	10	Policy, SDN-C	PCI 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

Pair-wise testing

SDNR_RAN_PAIRWISE_001Connecting SDN-R with RAN (Sim) (netconf servers)002Receiving neighbor list change notification from RANSDNR_PCIMS

Test case ID	Components	Test case	Status
1.	POLICY_OOF_PAIRWISE_001	Policy, OOF	(Initial) Configuration of OOF	Not tested
2.	POLICY_PCIMS_PAIRWISE_001	Policy, PCI-MS	(Initial) Configuration of PCI-MS	Not tested
3.	SDNR_RAN_PAIRWISE_001	SDN-R, RAN (Sim)	Connecting SDN-R with RAN (Sim) (netconf servers)	Not tested
4.	SDNR_RAN_PAIRWISE_002	SDN-R, RAN (Sim)	Receiving neighbor list change notification from RAN	Not tested
5.	SDNR_PCIMS_PAIRWISE_001	SDN-R, PCI-MS	Handle neighbor list change notification from SDN-R	Not tested
6.	SDNR_PCIMS_PAIRWISE_002	SDN-R, PCI-MS	Config DB API access (for getNbrList)	Not tested
7.	OOF_PCIMS_PAIRWISE_001	OOF, PCI-MS	Request for PCI optimization	Not tested
8.	OOF_SDNR_PAIRWISE_001	OOF, SDN-R	Config DB API access (for getNbrList)	Not tested
9.	OOF_PCIMS_PAIRWISE_002	OOF, PCI-MS	PCI optimization result	Not tested
10.	SDNR_PCIMS_PAIRWISE_003	SDN-R, PCI-MS	Config DB API access (for pnfName)	Not tested
11.	POLICY_PCIMS_PAIRWISE_002	Policy, PCI-MS	Sending DMaaP message by PCI-MS to Policy	Not tested
12.	POLICY_SDNR_PAIRWISE_001	Policy, SDN-R	Invoking control loop in Policy	Not tested
13.	SDNR_RAN_PAIRWISE_003
POLICY_OOF_PAIRWISE_001	Policy, OOF	(Initial) Configuration of OOF	Not tested
POLICY_PCIMS_PAIRWISE_001	Policy, PCI-MS	(Initial) Configuration of PCI-MS	Not tested
	SDN-R, RAN (Sim)	Send netconf message(s) to RAN-Sim with the PCI changes	Not tested
14.	SDNR_RAN_PAIRWISE_	004	SDN-R, RAN (Sim)	Successful update of PCI values	Not tested

OOF_PCIMS, PCI-MS

Test Case ID

 Anchor
POLICY_OOF_PAIRWISE_001

SDN-R, PCI-MS

Handle neighbor list change notification from SDN-R

Not tested

SDNR_PCIMS_PAIRWISE_002

SDN-R, PCI-MS

Config DB API access (for getNbrList)

Not tested

POLICY_OOF_PAIRWISE_001
POLICY_OOF

_PAIRWISE_001

Test Case Name

Configuration of OOF

Request for PCI optimization

Not tested

OOF_SDNR_PAIRWISE_001

OOF, SDN-R

Config DB API access (for getNbrList)

Not tested

OOF_PCIMS_PAIRWISE_002

OOF, PCI-MS

PCI optimization result

Not tested

SDNR_PCIMS_PAIRWISE_003

SDN-R, PCI-MS

Config DB API access (for pnfName)

Not tested

POLICY_PCIMS_PAIRWISE_002

Policy, PCI-MS

Sending DMaaP message by PCI-MS to Policy

Not tested

POLICY_SDNR_PAIRWISE_001

Policy, SDN-R

Invoking control loop in Policy

Not tested

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

Bring up the OOF using the installation steps.
Check the OOF database to see the contents of the OOF config policy for PCI optimization use case.

OOF comes online and the database and local datastructures for PCI optimization use case are initialized correctly.
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

 Anchor
POLICY_PCIMS_PAIRWISE_001
POLICY_PCIMS

Test Case ID

 Anchor
POLICY_OOF_PAIRWISE_001POLICY_OOF_PAIRWISE_001
POLICY_OOFPCIMS_PAIRWISE_001

Test Case Name

Configuration of OOFPCI-MS

Description

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

Release

Casablanca

Pre-conditions

(a) Policy module is onboarded.

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

Testing Steps

Steps

Expected Result

Bring up the OOF PCI-MS using the installation intallation steps.
Check the OOF PCI-MS database to see the contents of the OOF PCI-MS config policy for PCI optimization use case.

OOF PCI-MS comes online and the database and local datastructures for PCI optimization use case (e.g., thread pool) are initialized correctly.
Config-policy is correctly fetched and stored in the OOF PCI-MS DB.
Sample config policy contents are given below:
ALGO_CATEGORY:OOF-PCI-OPTIMIZATIONPCI_NEIGHBOR_CHANGE_CLUSTER_TIMEOUT_IN_SECS:60
PCI_OPTMIZATIONMODCONFIG_ALGOPOLICY_NAME:OOF-PCI-OPTIMIZATION-LEVEL1
PCI_OPTIMIZATION_NW_CONSTRAINT:MAX5PCICHANGESONLY
PCI_OPTIMIZATION_PRIORITY: 2
PCI_OPTIMIZATION_TIME_CONSTRAINT:NONEControlLoop-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

SDNR_RAN_PAIRWISE_001

Test Case ID

 Anchor
POLICYSDNR_PCIMSRAN_PAIRWISE_001POLICY
SDNR_PCIMSRAN_PAIRWISE_001
POLICYSDNR_PCIMSRAN_PAIRWISE_001

Test Case Name

Configuration of PCI-MS

Connecting SDN-R with RAN (netconf servers)

DescriptionTest

if the PCI-MS is onboarded and configuration policies are fetched and loaded correctly (Step 1b of flow)Establish connection between SDN-R and RAN

Release

Casablanca

Pre-conditions

(a) Policy module is onboarded.SDN-R is up and running

(b) Config policies related to PCI-MS are provisioned properly in Policy module.RAN initialization file is available

Testing Steps

Steps

Expected Result

Bring up the PCIRAN-MS Simulator using the intallation installation steps.
Check the PCI-MS database to see the contents of the PCI-MS config policy.

PCI-MS comes online and the database and local datastructures (e.g., thread pool) are initialized correctly.
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

Anchor

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

Bring up the RAN-Simulator using the installation steps.
Observe the connection status between SDN-R and netconf server(s)

RAN-Simulator is successfully instantiated. GUI also shows the appropriate topology view.
SDN-R and netconf servers are connected (RAN-Simulator sends a mount request (REST) for each netconf server.

Observe the connection status between SDN-R and netconf server(s)	RAN-Simulator is successfully instantiated. GUI also shows the appropriate topology view. 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

 Anchor
SDNR_RAN_PAIRWISE_002
SDNR_RAN_PAIRWISE_002
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

(c) GUI shows RAN topology view properly, GUI is able to show the details of a particular cell (PCI, neighbor list, CellId).

Testing Steps

Steps	Expected Result
Modify the neighbor list of a cell (via RAN simulator GUI) The netconf server to which the cell is connected to sends a netconf notification to SDN-R.	SDN-R updates the Config DB (neighbor list of the cell). SDN-R sends a DMaaP message to the PCI-MS with the topic PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO.

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
SDNR_PCIMS_PAIRWISE_001
SDNR_PCIMS_PAIRWISE_001
SDNR_PCIMS_PAIRWISE_001

Test Case Name

Handle neighbor list change notification from SDN-R

Description

Handle neighbor list change notification from SDN-R and form a cell cluster.

Release

Casablanca

Pre-conditions

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

(b) SDNR_RAN_PAIRWISE_002 has been completed, and neighbor list change notification has been received by SDN-R.

Testing Steps

Steps	Expected Result
SDN-R sends a DMaaP message to PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO. DMaaP client in PCI-MS receives the message and forwards it to the PCI-MS core for further processing.	DMaaP message is received by Main thread of PCI-MS (verify by viewing logs).

Conclusion (Pass /Fail)

Testing Lab

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

SDNR_RAN_PAIRWISE_002SDNR_PCIMS_PAIRWISE_001Handle neighbor list change notification from SDN-R

Test Case ID

 Anchor
SDNR_PCIMS_PAIRWISE_002
SDNR_PCIMS_PAIRWISE_002
SDNR_PCIMS_PAIRWISE_002

Test Case Name

Config DB API access

Description

Test the working of Config DB APIs

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

Anchor

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

(c) GUI shows RAN topology view properly, GUI is able to show the details of a particular cell (PCI, neighbor list, CellId).

Testing Steps

Steps	Expected Result
Modify the neighbor list of a cell (via RAN simulator GUI) The netconf server to which the cell is connected to sends a netconf notification to SDN-R.	SDN-R updates the Config DB (neighbor list of the cell). SDN-R sends a DMaaP message to the PCI-MS with the topic PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO.

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

Anchor

SDNR_PCIMS_PAIRWISE_001

Test Case Name

Description

Handle neighbor list change notification from SDN-R and form a cell cluster.

Release

Casablanca

Pre-conditions

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

(b) SDNR_RAN_PAIRWISE_002 has been completed, and neighbor list change notification has been received by SDN-R.(SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file.

(c) SDNR_PCIMS_PAIRWISE_001 has been completed (if not, write some stub code in PCI-MS to do the ConfigDB query after initialization).

Testing Steps

Steps

Expected Result

SDNPCI-R sends a DMaaP message to PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO.
DMaaP client in PCI-MS receives the message and forwards it to the PCI-MS core for further processing.

DMaaP message is received by Main thread of PCI-MS (verify by viewing logs)

MS does a query to the configDB using the getNbrList API to get the neighbor list.

API query is successful and results match with DB contents. API contents are provided in SDN-R impacts document.

Conclusion (Pass /Fail)

Testing Lab

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

OOF_PCI_PAIRWISE_001

Test Case ID

 Anchor
SDNROOF_PCIMS_PAIRWISE_002001SDNR
OOF_PCIMS_PAIRWISE_002001
SDNROOF_PCIMSPCI_PAIRWISE_002001

Test Case Name

Config DB API access

Request for PCI optimization

Description

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

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.

(c) SDNR_PCIMS_PAIRWISE_001 002 has been completed (if not, write some stub code otherwise some dummy code for REST API call to OOF to be written in PCI-MS to do the ConfigDB query after initialization).

Testing Steps

Steps	Expected Result
After receiving neighbor list change notification from SDN-R, PCI-MS does a query to the configDB using the getNbrList API to get the neighbor list.API query is successful and results match with DB contents. API contents are provided in SDN-R impacts document.

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

Anchor

OOF_PCIMS_PAIRWISE_001

processes it and determines OOF to be called.
PCI-MS invokes the OOF PCI API (https://{host}:{port}/api/oof/v1/pci) for executing the PCI optimization.
An example of the API contents is available in PCI Optimization API

OOF accepts the API request and sends a 200 OK response. An example of the (synchronous) response contents is available in PCI Optimization API

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
OOF_SDNR_PAIRWISE_001
OOF_SDNR_PAIRWISE_001
OOF_SDNR_PAIRWISE_001

Test Case Name

Config DB API access by OOF

Description

Accessing Config DB APIs by OOF for PCI optimization algorithm execution

Release

Casablanca

Pre-conditions

(a) OOF has fetched the config policies successfully from the Policy module.

(b) OOF_PCIMS_PAIRWISE_001 has been completed successfully (otherwise some dummy code for REST API call to Config DB to be written in OOF).

Testing Steps

Steps

Expected Result

After receiving a request for PCI optimization, OOF does a Config DB API query for getting the cellList (for a given networkID) and nbrList (for the set of cells sent in the PCI optimization request by PCI-MS).
API contents are available in SDN-R impacts document.

SDN-R accepts the API and sends a response with the requested details.

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.

(c) SDNR_PCIMS_PAIRWISE_002 has been completed (otherwise some dummy code for REST API call to OOF to be written in PCI-MS).

Testing Steps

Steps	Expected Result
After receiving neighbor list change notification from SDN-R, PCI-MS processes it and determines OOF to be called. PCI-MS invokes the OOF PCI API (https://{host}:{port}/api/oof/v1/pci) for executing the PCI optimization. An example of the API contents is available in PCI Optimization API	OOF accepts the API request and sends a 200 OK response. An example of the (synchronous) response contents is available in PCI Optimization API

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
OOF_SDNRPCIMS_PAIRWISE_001002
OOF_SDNRPCIMS_PAIRWISE_001002
OOF_SDNRPCIMS_PAIRWISE_001002

Test Case NameConfig DB API access

PCI optimization result reported by OOF to PCI-MS

DescriptionAccessing Config DB APIs

PCI optimization result sent by OOF to PCI-MS via REST call.

for PCI optimization algorithm execution

Release

Casablanca

Pre-conditions

(a) OOF 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.

(c) OOF_PCIMS_PAIRWISE_001 has been completed successfully (otherwise some dummy code for REST API call to Config DB PCI-MS to be written in OOF).

Testing Steps

Steps	Expected Result
After receiving a request for executing the PCI optimization algorithm, OOF does a Config DB API query for getting the cellList (for a given networkID) and nbrList (for the set of cells sent in the PCI optimization request by PCI-MS). API contents are available in SDN-R impacts document. invokes the callback API provided by the PCI-MS in the PCI optimization request API call. This API contains the results of the PCI optimization, i.e., the cells whose PCI values should be modified. An example of the API contents is available in PCI Optimization API	PCI-MS SDN-R accepts the API and sends a 200 OK response with the requested details.

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
OOFSDNR_PCIMS_PAIRWISE_002003OOF
SDNR_PCIMS_PAIRWISE_002003
OOFSDNR_PCIMS_PAIRWISE_002003

Test Case Name

Config DB API access

Description

Test the working of Config DB APIs (getPnfName)

PCI optimization result reported by OOF to PCI-MS

Description

PCI optimization result sent by OOF to PCI-MS via REST call.

Release

Casablanca

Pre-conditions

(a) OOF 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.

(c) OOF_PCIMS_PAIRWISE_001 002 has been completed (otherwise some dummy code for REST API call to if not, write some stub code in PCI-MS to be written in OOFdo the ConfigDB query).

Testing Steps

Steps	Expected Result
For the list of cells (whose PCI values should be changed) received from OOF in the PCI-optimization result, PCI-MS does a query to the configDB using the getPnfName for obtaining the PNF names for those cells whose PNF names are not available in its local DB.	API query is successful and results match with DB contents. API details are provided in SDN-R impacts document	After executing the PCI optimization algorithm, OOF invokes the callback API provided by the PCI-MS in the PCI optimization request API call. This API contains the results of the PCI optimization, i.e., the cells whose PCI values should be modified. An example of the API contents is available in PCI Optimization API	PCI-MS accepts the API and sends a 200 OK response .

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

Anchor

SDNR

	POLICY_PCIMS_PAIRWISE_

003

002

SDNR

	POLICY_PCIMS_PAIRWISE_

003

002

SDNR

POLICY_PCIMS_PAIRWISE_

003

002
Test Case Name

Config DB API access

Sending DMaaP message to Policy module with the PCI changes.

Description

Test the working of Config DB APIs (getPnfName)

Sending of DMaaP message (Topic: DCAE_EVENT_OUTPUT) by PCI-MS to Policy with the PCI changes

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.

(c)

OOF

SDNR_PCIMS_PAIRWISE_

002

003 has been completed (if not, write some stub code in PCI-MS to

do

send the

ConfigDB query

DMaaP message).

Testing Steps

Steps	Expected Result

For the list of cells (whose PCI values should be changed) received from OOF in the PCI-optimization result, PCI-MS does a query to the configDB using the getPnfName for obtaining the PNF names for those cells whose PNF names are not available in its local DB.

PCI-MS prepares the DMaaP message (with payload layout corresponding to the yang model) to be sent to Policy. It sends 1 message for each PNF.

DMaaP message(s) is successfully received by Policy.

API query is successful and results match with DB contents. API details are provided in SDN-R impacts document.

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
POLICY_

PCIMS

SDNR_PAIRWISE_

002

001
POLICY_

PCIMS

SDNR_PAIRWISE_

002

001
POLICY_

PCIMS

SDNR_PAIRWISE_

002

001
Test Case Name

Sending

	Invoking the control loop in Policy
Description	Invoking the control loop and sending DMaaP message to

Policy module

SDN-R with the PCI changes.

Description

Sending of DMaaP message (Topic: DCAE_EVENT_OUTPUT) by PCI-MS to Policy with the PCI changes


Release	Casablanca
Pre-conditions	(a) Control Loop Policy is successfully loaded and configured in

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

is initialized, configured and connected to the RAN-Sim (netconf servers).

(c)

SDNR

POLICY_PCIMS_PAIRWISE_

003

002 has been completed

(if not, write some stub code in PCI-MS to send the DMaaP message)

.

Testing Steps

Steps	Expected Result

PCI-MS

Policy executes the control loop for PCI use case, and prepares the DMaaP message (

with

topic - SDNR-CL, and payload layout

corresponding to the

taken from the DMaaP message received from PCI-MS) to the yang model) to be sent to Policy. It sends 1 message for each PNF. SDNR-CL

DMaaP message(s) is successfully received by

Policy

SDN-R.

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
POLICYSDNR_SDNRRAN_PAIRWISE_001003POLICY
SDNR_SDNRRAN_PAIRWISE_001003
POLICYSDNR_SDNRRAN_PAIRWISE_001003

Test Case Name

Invoking the control loop in Policy

Sending message(s) to RAN-Sim to update PCI values

Description

SDN-R sending netconf (edit-config) message(s) to RAN-Sim to update the PCI values

Description

Invoking the control loop and sending DMaaP message to SDN-R with the PCI changes.

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy moduleSDN-R is initialized, configured and connected to the RAN-Sim (netconf servers).

(b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file.RAN-Sim is initialized and configured properly.

(c) POLICY_SDNR_PAIRWISE_001 has been completed.

(d) SDNR_RAN_PAIRWISE_002 has been completed(c) SDNR_PCIMS_PAIRWISE_003 has been completed (if not, write some stub code in PCI-MS to send the DMaaP message).

Testing Steps

Steps	Expected Result
PCI-MS Policy executes the control loop for PCI use case, and prepares the DMaaP message (with payload layout corresponding topic - SDNR-CL, and payload layout taken from the DMaaP message received from PCI-MS) to the yang model) to be sent to Policy. It sends 1 message for each PNF. DMaaP message(s) is successfully received by PolicySDNR-CL	RAN-Sim receives the message, and makes necessary updates to the PCI values (GUI reflects these changes).

Conclusion (Pass /Fail)

Testing Lab

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

Test Case ID

 Anchor
SDNR_RAN_PAIRWISE_004
SDNR_RAN_PAIRWISE_004
SDNR_RAN_PAIRWISE_004

Test Case Name

Acknowledgement of successful update of PCI values.

Description

RAN-Sim sending success response to netconf (edit-config) message(s) to SDN-R.

Release

Casablanca

Pre-conditions

(a) SDN-R is initialized, configured and connected to the RAN-Sim (netconf servers).

(b) RAN-Sim is initialized and configured properly.

(d) SDNR_RAN_PAIRWISE_003 has been completed.

Testing Steps

Steps	Expected Result
RAN-Sim sends a success response to SDN-R upon receipt of netconf edit-config message from SDN-R. Upon receipt of this response, SDN-R prepares a DMaaP message (Topic: SDNR-CL-RSP)	Policy receives the DMaaP message, and the Control Loop status can be viewed in the logs.

Conclusion (Pass /Fail)

Testing Lab

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

Integration Testing

Use case Step	Component(s)	Functionality	Test case	Impacted API	Status
5	PCI-Handler MS, OOF	Request 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
6	OOF, Policy	Fetch 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
7	OOF, SDN-C	Fetch 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
9	PCI-Handler MS, Policy	Recommended 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
10	Policy, SDN-C	PCI 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

Space shortcuts

Page tree

Versions Compared

Old Version 20

New Version 21

Key

Pair-wise testing

Integration Testing

Pair-wise testing

Integration Testing

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 20

New Version 21

Key

Pair-wise testing

Integration Testing

Pair-wise testing

Integration Testing