Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	Key in (REQ-53, REQ-96, REQ-92, req-88, req-84) ORDER BY assignee DESC
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

Development Tickets

...

id	Development Status

...

Scenario 1 Using

...

direct Netconf/Yang interface with PNF

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions
maximumIssues	50
jqlQuery	"epic link" = INT-1131
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Scenario 2

...

Enable service level LCM operations

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions
maximumIssues	20
jqlQuery	"epic link" = req-88
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Scenario 3 Using

...

Ansible protocol

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	"epic link" = INT-1207
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Scenario 4

...

Netconf/Yang interface with EM

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	"epic link"=INT-1212
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

Test Status

1	There should be a test case for each item in the sequence diagram	NOT YET TESTED
2	create additional requirements as needed for each discreet step	COMPLETE
3	Test cases should cover entire Use Case	PARTIALLY COMPLETE
4	Test Cases should include enough detail for testing team to implement the test	FAILED

...

id	Test Status

...

Test Cases should include enough detail for testing team to implement the test

FAILED

Scenario 1 Using direct Netconf/Yang interface with PNF

PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases
Jira Legacy
showSummary false
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key INT-1308

Test Case Id	Test Case	Test Type	Status
TEST-CASE-1	Test Check in SDNC certificates to connect node are properly installed	Integration(robot)	COMPLETE
TEST-CASE-2	Test Blue print archive is properly uploaded to blueprint-processor	Integration(robot)	COMPLETE
TEST-CASE-3	Test resource package and service is successfully distributed from SDC to SO	Integration(robot)	COMPLETE
TEST-CASE-4	Test all the pnf workflows are successfully fetched from SO	Integration(robot)	COMPLETE
TEST-CASE-5	Test Service instantiation is triggered from VID to SO and status is COMPLETED for preparation(Download) workflow	Integration(robot)	COMPLETE
TEST-CASE-6	Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETED	Integration(robot)	COMPLETE
TEST-CASE-7	Test Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflow	Integration(robot)	COMPLETE
TEST-CASE-8	Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETED	Integration(robot)	COMPLETE
TEST-CASE-9	Verify on AAI-Simulator that for pnf PNFDemo sw-version is pnf_sw_version-3.0.0.	Integration(robot)	COMPLETE

Test Cases Details:

All the test cases for Scenario 1 are robot tests that can be ran automatically from the same steps which will be shown below.

Testing Steps

#	Step	Expected Result
1	In the Integration csit repo, run plans/usecases/pnf-sw-upgrade robot tests	Pnf-sw-upgrade robot tests running
2	Wait for the tests to finish	Tests finished without timeout
3	Check the test reports	All test cases run successfully

Status (Pass/Fail)

ONAP Jira Ticket:

· https://jira.onap.org/browse/INT-1308

ONAP PNF SW Upgrade Daily CSIT Tests:

· https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/usecases-master-verify-csit-pnf-sw-upgrade/17/log.html.gz

Testing Lab

CSIT PNF SW Upgrade https://jenkins.onap.org/job/usecases-master-verify-csit-pnf-sw-upgrade/

Test Case ID	Test Case Name	Description	Release
TEST-CASE-1	Test Check in SDNC certificates to connect node are properly installed	This test will check whether the keystore is setup and certificates installed for SDNC and ODL once SDNC is installed	Frankfurt
TEST-CASE-2	Test Blueprint archive is properly uploaded to blueprint-processor	Test Blueprint archive is properly uploaded to blueprint-processor	Frankfurt
TEST-CASE-3	Test resource package and service is successfully distributed from SDC to SO	Test resource package and service is successfully distributed from SDC to SO	Frankfurt
TEST-CASE-4	Test all the PNF workflows are successfully fetched from SO	Test all the PNF workflows are successfully fetched from SO	Frankfurt
TEST-CASE-5	Test Service instantiation is triggered from VID to SO and status is COMPLETED for preparation (Download) workflow	Test Service instantiation is triggered from VID to SO and status is COMPLETED for preparation (Download) workflow	Frankfurt
TEST-CASE-6	Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETED	Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETED	Frankfurt
TEST-CASE-7	Test Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflow	Test Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflow	Frankfurt
TEST-CASE-8	Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETED	Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETED	Frankfurt
TEST-CASE-9	Verify on AAI-Simulator that for pnf PNFDDemo sw-version is pnf_sw_version-3.0.0	Verify on AAI-Simulator that for pnf PNFDDemo sw-version is pnf_sw_version-3.0.

...

Frankfurt

...

0

Frankfurt

Scenario 2 Enable service level LCM operations

PNF Software Information On boarding Test Cases

Test Case Id

Test Case

Test Type

Status

TEST-CASE-1

Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-API test

Sanity

Local SDC deployment: COMPLETE

SDC Daily API Sanity: COMPLETE

TEST-CASE-2

Test Onboarding of PNF Package with non-mano Software Information in SDC GUI

Manual

Local SDC deployment: COMPLETE

TEST-CASE-3

Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-UI test

Sanity

Local SDC deployment: COMPLETE

SDC Daily UI Sanity: COMPLETE

Test Types:

Sanity-API: automated sanity tests for backend SDC APIs (SDC Sanity);
Sanity-UI: automated sanity tests for SDC GUI;
Manual: manual test in SDC UI (either local SDC or ONAP deployment);
End to End (E2E): end to end test with other interested ONAP components.

Test Cases Details

Test Case ID

TEST-CASE-1
Anchor
test-case-1
test-case-1

Test Case Name

Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-API test

Description

The test will onboard PNF Packages with non-mano Software Information in the SDC Sanity API test flow

Release

Frankfurt

Preconditions

Local SDC or ONAP deployment available and running

Testing Steps

#	Step	Expected Result
1	Run SDC sdc-api-tests	sdc-api-tests running
2	Wait for the tests to finish	Tests finished without timeout
3	Check the test reports	All test cases run successfully

Status (Pass/Fail)

Local SDC deployment: COMPLETE

https://jira.onap.org/browse/SDC-2641

SDC Daily API Sanity: COMPLETE

Testing Lab

Local SDC deployment, SDC Daily API Sanity run https://jenkins.onap.org/view/sdc/job/sdc-master-verify-csit-sanity-testng/

Test Case ID

TEST-CASE-2
Anchor
test-case-2
test-case-2

Test Case Name

Test Onboarding of PNF Package with non-mano Software Information in SDC GUI

Description

Manually onboard the PNF Package with non-mano Software Information in the SDC GUI, creating a VSP and importing as a ONAP PNF Resource.

Release

Frankfurt

Preconditions

Local SDC or ONAP deployment available and running;
A SDC Vendor License Model already created;
A valid PNF Package with non-mano Software Information.

Testing Steps

#	Step	Expected Result
1	Access SDC GUI as a Designer.	SDC Home screen is shown.
2	Go to the Onboard Workspace .	Onboard workspace is shown.
3	Click on "CREATE NEW VSP".	"New Software Product" popup is shown.
4	Fill in the "New Software Product" required information, selecting "Network Package" as the Onboarding Procedure and click on create.	The VSP Overview page is shown.
5	In the VSP Overview screen, Software Product Attachments, click on select file and provide the PNF Package with non-mano Software Information.	The VSP attachment validation screen is shown.
6	In the VSP attachment validation, click on the Submit button.	A "Commit & Submit" popup is shown.
7	Fill the "Commit & Submit" popup with any comment and click in the "Commit & Submit" button.	A "Submit Succeeded" information is shown.
8	Close the "Submit Succeeded" popup and go to the Home workspace.	SDC Home screen is shown.
9	Hover your mouse to the IMPORT square and click in "Import VSP".	A "Import VSP" modal is shown with the SDC VSP list.
10	Search for the created VSP.	The created VSP is shown in the VSP list.
11	Click on the VSP and then in the Download VSP link.	The VSP CSAR package is downloaded.
12	Open the CSAR package and check that the software information artifact is present in the folder Artifacts/Informational/PNF_SW_INFORMATION.	The onboarded artifact is present on the folder.
13	Go back to the "Import VSP" modal and click on the "Import VSP" link.	The Resource Design General page is open with the PNF package information.
14	Click on the "Create" button to create the resource.	A creation confirmation message is shown.
15	On the left panel, click on the "Properties Assignment".	The "Properties Assignment" page is shown.
16	Verify that the "software_versions" property is present and filled with the versions provided in the software information artifact.	The "software_versions" property is present with the expected content.

Status (Pass/Fail)

Local SDC deployment: COMPLETE

Used package: onboarding-package.csar

Image Modified

Test case recording: Onboard_PNF_Software_Version.mkv

Testing Lab

Local SDC deployment

Test Case ID

TEST-CASE-3
Anchor
test-case-3
test-case-3

Test Case Name

Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-UI test

Description

The test will onboard the PNF Package with non-mano Software Information in the UI SDC Sanity test flow

Release

Frankfurt

Preconditions

Local SDC or ONAP deployment available and running

Testing Steps

#	Step	Expected Result
1	Run SDC sdc-ui-tests	sdc-ui-tests running
2	Wait for the tests to finish	Tests finished without timeout
3	Check the test reports	All test cases run successfully

Status (Pass/Fail)

Local SDC deployment: COMPLETE

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	SDC-2702

SDC Daily UI Sanity: COMPLETE https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/sdc-master-csit-uiSanity-testng/1102/SDC_UI_Extent_Report.html.gz

Testing Lab

Local SDC deployment, SDC Daily UI Sanity run https://jenkins.onap.org/view/sdc/job/sdc-master-csit-uiSanity-testng/

...

Scenario 3 Using

...

Ansible protocol

PNF Software Upgrade Using Ansible with EM Test Cases

Test Case Id	Test Case	Test Status
TEST-CASE-1	UpgradePreCheck for PNF instance from SDNC to EM using LCM API	COMPLETE
TEST-CASE-2	DownloadNESw for PNF instance from SDNC to EM using LCM API	COMPLETE
TEST-CASE-3	ActivateNESw for PNF instance from SDNC to EM using LCM API	COMPLETE
TEST-CASE-4	UpgradePostCheck for PNF instance from SDNC to EM using LCM API	COMPLETE
TEST-CASE-5	Test PNF SW upgrade Workflow for PNF instance from SO to SDNC (using LCM API) to EM	COMPLETE

Details at Enhancement on PNF S/W Upgrade using Ansible.

...

Scenario 4

...

Netconf/Yang interface with EM

PNF Software Upgrade Using Netconf/Yang Interface with EM Test Cases

Test Case Id	Test Case	Test Status
TEST-CASE-1	Download NE SW for PNF instance 1 from CDS to EM using SS REST API	COMPLETE
TEST-CASE-2	Activate NE SW for PNF instance 1 from CDS to EM using SS REST API	COMPLETE
TEST-CASE-3	Download NE SW for PNF instance 2 from CDS to EM using SS REST AP	COMPLETE
TEST-CASE-4	Activate NE SW for PNF instance 2 from CDS to EM using SS REST API	COMPLETE
TEST-CASE-5	Test PNF SW upgrade Workflow for PNF instance 1 from SO to CDS (using SS gRPC API) to EM	COMPLETE

Details at PNF software upgrade with Netconf/Yang interface with EM.

Reference

ONAP Controller Evolution Consideration - LCM APIs

...

Version	Old Version 127	New Version 128
Changes made by	Zu Qiang	Zu Qiang
Saved on	Apr 20, 2020	Apr 20, 2020

Content Comparison

Versions Compared

Key

Development Tickets

Scenario 1 Using

direct Netconf/Yang interface with PNF

Scenario 2

Enable service level LCM operations

Scenario 3 Using

Ansible protocol

Scenario 4

Netconf/Yang interface with EM

Test Status

Scenario 1 Using direct Netconf/Yang interface with PNF

PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases Jira LegacyshowSummaryfalseserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyINT-1308

Scenario 2 Enable service level LCM operations

PNF Software Information On boarding Test Cases

Test Cases Details

TEST-CASE-1 Anchortest-case-1test-case-1

TEST-CASE-2 Anchortest-case-2test-case-2

TEST-CASE-3 Anchortest-case-3test-case-3

Scenario 3 Using

Ansible protocol

PNF Software Upgrade Using Ansible with EM Test Cases

Scenario 4

Netconf/Yang interface with EM

PNF Software Upgrade Using Netconf/Yang Interface with EM Test Cases

Reference

PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases
Jira Legacy
showSummary false
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key INT-1308

TEST-CASE-1
Anchor
test-case-1
test-case-1

TEST-CASE-2
Anchor
test-case-2
test-case-2

TEST-CASE-3
Anchor
test-case-3
test-case-3