...

Sanity Docker executed as part of our Docker run script and will be started automatically on demand as part of other Dockers init process by default.

Executing example:

/data/scripts/docker_run.sh -r 1.1-stagging-lates

will trigger the sanity docker execution after the components have started.

There is an option to cancel sanity execution by using  –s flag to start Docker run script.

Executing example:

/data/scripts/docker_run.sh -s -r 1.1-stagging-lates

latest -t

-t flag meaning start sanity docker 

About onboarding E2E flow:

...

• Onboard of VNF
• Create VF from VSP
• Certify VF 
• Create Service
• Add VF to service

• Certify Service

• Export TOSCA and validate it structure using external TOSCA parser

**as part of execution we open a connection to Titan and perform resources clean up both before and after tests execution (only resource with “ci” prefix will be deleted from the catalog)

List of VNFs/PNFs that proceed by onboarding flow:

• vCPE_Infra.zip
• vCPE_Vbng.zip
• vCPE_Vbrgemu.zip
• vCPE_Vgmux.zip
• vCPE_Vgw.zip
• base_clearwatersample-signed-pnf-cms-includes-cert-1.0.1-SNAPSHOT.zip
• sample-signed-pnf-1.0.1-SNAPSHOT.zip
• sample-pnf-1.0.1-SNAPSHOT.csar
• sample-pnf-custom-type.csar
• vbng.zip
• vgmux.zip
• vfw.zip
• vvg.zip
• base_vvg.zip
• vLBMS.zip
• vgw.zip
• infra.zip
• vLB.zip
• base_vfw.zip
• vbrgemu.zip
• base_vlb.zip
• base_vvg.zipresource-ZteEpcMmeVf-csar_fix.csar
• ZteEpcMmeVf.csa
• Huawei_vHSS.csar
• vSBC_update_v03.csar
• Huawei_vMME.csar
• vsp-vgw.csar
• database-substitution-mappings.csar

Execution time:

Current tests execution time is ~2min ~7min – this includes onboarding of 5 VNFs 22 VNF/PNF running in 2 threads1 thread

Report location:

/data/logs/sdc-sanity-api-tests/ExtentReport/
/data/logs/sdc-ui-tests/ExtentReport/

Report example:

Image Added

CSIT:

SDC plans to leverage our internal sanity docker as part of the CSframeworkork. we will be executing the docker from the CSIT and storing the results

Future inchantments:

1. SDC plans to add ui testing capabelties to capabilities to our sanity docker by changing the docker os and adding Selenium.
   the The UI testing will leverage the exicting java selanuem exciting java selenium test already avilable available in the SDC code base.
    

   Jira Legacy
   showSummary true server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SDC-384

2. SDC planse plans to change the flow  of flow of the tests so that the test input will be dynamicly retrived from dynamically retrieved from the vnf repo instade instead of placing the input in the docker itself,
   this way we will be able to re exacute execute the test with updated inputs with our without creating a new Docker image..
   

   Jira Legacy
   server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SDC-385

...