Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Introduction

SDC sanity Docker is a part of our system and it aim is to issue 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

  • There is an option to cancel it startup by adding –s flag to start Docker run script.

    TBD


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)

List of VNFs that proceed by onboarding flow

  • vCPE_Infra.zip
  • vCPE_Vbng.zip
  • vCPE_Vbrgemu.zip
  • vCPE_Vgmux.zip
  • vCPE_Vgw.zip

Execution time 

Current tests execution time is ~2min – this includes onboarding of 5 VNFs running in 2 threads

Repot location 


/data/logs/sdc-sanity/ExtentReport
  • No labels