Versions Compared

Version Old Version 120 New Version 121
Changes made by

Darragh Egan

Rahul Tyagi

Saved on

Key

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

...

Deck
idDevelopment Status


Card
defaulttrue
title-old PNF software upgrade with direct Netconf/Yang interface with PNF
labelScenario 1 Using direct Netconf/Yang interface with PNF
title PNF software upgrade with direct Netconf/Yang interface with PNF

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions
maximumIssues50
jqlQuery"epic link" = INT-1131
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Card
title-oldEnable service level LCM operations
labelScenario 2 Enable service level LCM operations
titleEnable service level LCM operations

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions
maximumIssues20
jqlQuery"epic link" = req-88
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Card
title-oldEnhancement on the PNF upgrade using Ansible protocol
labelScenario 3 Using Ansible protocol
titleEnhancement on the PNF upgrade using Ansible protocol

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuery"epic link" = INT-1207
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Card
title-oldPNF software upgrade with Netconf/Yang interface with EM
labelScenario 4 Netconf/Yang interface with EM
titlePNF software upgrade with Netconf/Yang interface with EM

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuery"epic link"=INT-1212
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Test Status

1There should be a test case for each item in the sequence diagram

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

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

 FAILED

...

NOT YET TESTED
Deck
idTest Status


NOT YET TESTED
Card
defaulttrue
title-old PNF software upgrade with direct Netconf/Yang interface with PNF
labelScenario 1 Using direct Netconf/Yang interface with PNF
title PNF software upgrade with direct Netconf/Yang interface with PNF

PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases

Test Case IdTest CaseTest TypeStatus
TEST-CASE-1Test
resource package and service is successfully distributed from SDC to SO
Integration
Check in SDNC certificates to connect node are properly installed Integration(robot)COMPLETE
TEST-CASE-2Test
Service instantiation is triggered from VID to SO and accepted by SO 		Integration
Blue print archive is properly uploaded to blueprint-processorIntegration(robot)COMPLETE
TEST-CASE-3Test
PNF softoware upgrade Workflow is triggered and precheck building block sends correct request to CDSIntegrationNOT YET TESTED
resource package and service is successfully distributed from SDC to SOIntegration(robot)

COMPLETE

TEST-CASE-4Test
PNF softoware upgrade Workflow is triggered and downloadSwNE building block sends correct request to CDSIntegration NOT YET TESTED
all the pnf workflows are successfully fetched from SOIntegration(robot)COMPLETE
TEST-CASE-5Test
Correct software is downloaded on Simulator and it send expected response to cdsIntegrationNOT YET TESTEDNOT YET TESTED
Service instantiation is triggered from VID to SO and status is COMPLETED for preparation(Download) workflowIntegration(robot)COMPLETE
TEST-CASE-6
Test PNF softoware upgrade Workflow is triggered and ActivateSwNE building block sends correct request to CDSIntegration
Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETEDIntegration(robot)COMPLETE
TEST-CASE-7Test
Correct software is activated on Simulator and it send expected response to cds and its being updated in A&AIIntegrationNOT YET TESTEDNOT YET TESTED
Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflowIntegration(robot)COMPLETE
TEST-CASE-8
Test PNF softoware upgrade Workflow is triggered and postcheck building block sends correct request to CDSIntegration
Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETEDIntegration(robot)COMPLETE
TEST-CASE-9Verify on AAI-Simulator that for pnf PNFDemo sw-version is pnf_sw_version-3.0.0.Integration(robot)COMPLETE



Card
title-oldEnable service level LCM operations
labelScenario 2 Enable service level LCM operations
titleEnable service level LCM operations

PNF Software Information On boarding Test Cases

Test Case IdTest CaseTest TypeStatus
TEST-CASE-1Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-API testSanity

Local SDC deployment: COMPLETE

SDC Daily API Sanity: COMPLETE

TEST-CASE-2Test Onboarding of PNF Package with non-mano Software Information in SDC GUIManualLocal SDC deployment: COMPLETE
TEST-CASE-3Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-UI testSanity

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 NameTest Onboarding of PNF Package with non-mano Software Information in SDC Sanity-API test
DescriptionThe test will onboard PNF Packages with non-mano Software Information in the SDC Sanity API test flow
ReleaseFrankfurt
Preconditions

Local SDC or ONAP deployment available and running

Testing Steps


#StepExpected Result
1

Run SDC sdc-api-tests

sdc-api-tests running
2

Wait for the tests to finish

Tests finished without timeout
3Check the test reportsAll test cases run successfully


Status (Pass/Fail)

Local SDC deployment: COMPLETE

SDC Daily API Sanity: COMPLETE

Testing LabLocal 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 NameTest Onboarding of PNF Package with non-mano Software Information in SDC GUI
DescriptionManually onboard the PNF Package with non-mano Software Information in the SDC GUI, creating a VSP and importing as a ONAP PNF Resource.
ReleaseFrankfurt
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


#StepExpected Result
1

Access SDC GUI as a Designer.

SDC Home screen is shown.

2

Go to the Onboard Workspace .

Onboard workspace is shown.
3Click on "CREATE NEW VSP"."New Software Product" popup is shown.
4Fill in the "New Software Product" required information, selecting "Network Package" as the Onboarding Procedure and click on create.The VSP Overview page is shown.
5In 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.
6In the VSP attachment validation, click on the Submit button.A "Commit & Submit" popup is shown.
7Fill the "Commit & Submit" popup with any comment and click in the "Commit & Submit" button.A "Submit Succeeded" information is shown.
8Close the "Submit Succeeded" popup and go to the Home workspace.SDC Home screen is shown.
9Hover your mouse to the IMPORT square and click in "Import VSP".A "Import VSP" modal is shown with the SDC VSP list.
10Search for the created VSP.The created VSP is shown in the VSP list.
11Click on the VSP and then in the Download VSP link.The VSP CSAR package is downloaded.
12Open 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.
13Go 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.
14Click on the "Create" button to create the resource.A creation confirmation message is shown.
15On the left panel, click on the "Properties Assignment".The "Properties Assignment" page is shown.
16Verify 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

Test case recording: Onboard_PNF_Software_Version.mkv

Testing LabLocal SDC deployment


Test Case ID
  • TEST-CASE-3
    Anchor
    test-case-3
    test-case-3
Test Case NameTest Onboarding of PNF Package with non-mano Software Information in SDC Sanity-UI test
DescriptionThe test will onboard the PNF Package with non-mano Software Information in the UI SDC Sanity test flow
ReleaseFrankfurt
Preconditions

Local SDC or ONAP deployment available and running

Testing Steps


#StepExpected Result
1

Run SDC sdc-ui-tests

sdc-ui-tests running
2

Wait for the tests to finish

Tests finished without timeout
3Check the test reportsAll test cases run successfully


Status (Pass/Fail)

Local SDC deployment: COMPLETE 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-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 LabLocal SDC deployment, SDC Daily UI Sanity run https://jenkins.onap.org/view/sdc/job/sdc-master-csit-uiSanity-testng/



Card
title-oldEnhancement on the PNF upgrade using Ansible protocol
labelScenario 3 Using Ansible protocol
titleEnhancement on the PNF upgrade using Ansible protocol

TBD


Card
title-oldPNF software upgrade with Netconf/Yang interface with EM
labelScenario 4 Netconf/Yang interface with EM
titlePNF software upgrade with Netconf/Yang interface with EM

TBD


...