Introduction
SDC sanity Docker is a part of our system and its aim is to create a suite of tests that will perform a basic E2E flow (Onboarding).
Docker execution
Sanity Docker executed as part of our Docker run script and will be started automatically 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
About onboarding E2E flow:
Onboarding E2E flow cover following SDC functionality:
- Onboard of VNF
- Create VF from VSP
- Certify VF
- Create Service
- Add VF to service
Certify Service
**as part of execution we open 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 that proceed by onboarding flow:
- vCPE_Infra.zip
- vCPE_Vbng.zip
- vCPE_Vbrgemu.zip
- vCPE_Vgmux.zip
- vCPE_Vgw.zip
- base_clearwater.zip
- base_vfw.zip
- base_vlb.zip
- base_vvg.zip
Execution time:
Current tests execution time is ~2min – this includes onboarding of 5 VNFs running in 2 threads
Report location:
/data/logs/sdc-sanity/ExtentReport
Report example:
CSIT:
SDC plans to leverage our internal sanity docker as part of the CSframeworkork. we will be exacuting the docker from the CSIT and storing the results
Future inchantments:
- SDC plans to add ui testing capabelties to our sanity docker by changing the docker os and adding Selenium.
the UI testing will leverage the exicting java selanuem test already avilable in the SDC code base.
SDC-384 - Getting issue details... STATUS - SDC planse to change the flow of the tests so that the test input will be dynamicly retrived from the vnf repo instade of placing the input in the docker itself,
this way we will be able to re exacute the test with updated inputs with our creating a new Docker image.
SDC-385 - Getting issue details... STATUS