Versions Compared

Version Old Version 5 New Version Current
Changes made by

Ahila P

Ahila P

Saved on

Key

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

In I-release, test automation for new E2E Slice creation is targeted. This will be done in two steps.

  1. Prerequisites Automation 
  2. Use case flow automation

1. Dependent components

Except Config DB and RAN Simulator, all the other components follow helm based deployment. Config DB needs to be containerized and Ran Simulator is a dockerized spring boot application. 

  1. SDC
  2. SO
    1. dmaap
    2. mariadb
  3. CDS
  4. Multicloud
  5. EXT-API
  6. OOF
  7. Policy
  8. AAI
  9. SDN-R
  10. Config DBDB 
  11. RAN Simulator
    1. ransim controller
    2. honeycomb

2. Automation

2.1. Prerequisites set up automation

Automate the steps mentioned in Manual Configurations

2.2. Use case flow automation - E2E

...

new slice creation

Scenario1: Send request from CSMF to NSMF

Prerequisites:

  1. Components mentioned in the Section 1 (Dependent components) should be up and running

  2. Section 2.1 (Prerequisites set up automation) should be completed

  3. Execute the script to Script to input the slice profiles returned from OOF to NSSMFs and to feed the AN and CN endpoints to TN NSSMF ( for manual inputs in the E2E flow)

Entrypoint:

  1. Send a request to CSMF
  2. Execute the script to pass the slice profiles to NSSMFs and endpoints to TN NSSMF

Success Criteria:

  1. Check the request DB for the request completedness.completeness
  2. Verify the sync response
  3. Verify the below in AAI
    1. Service Profile creation in AAI
    2. Relationship between NSI and Service Profile
    3. Relationship between RAN Slice Profile and Service Profile
    4. Relationship between RAN Slice Profile and RAN NSSI
    5. Relationship between NSI and RAN NSSI
    6. Relationship between RAN NF Slice Profile and RAN NF NSSI
    7. Relationship between RAN NSSI and RAN NF NSSI
    8. Relationship between TN-FH Slice Profile and RAN Slice Profile
    9. Relationship between TN-FH Slice Profile and TN-FH NSSI
    10. Relationship between TN-FH NSSI and RAN NSSI
    11. Relationship between TN-MH Slice Profile and RAN Slice Profile
    12. Relationship between TN-MH Slice Profile and TN-MH NSSI
    13. Relationship between TN-MH NSSI and RAN NSSI
    14. Relationship between Core Slice Profile and Service Profile
    15. Relationship between Core Slice Profile and Core NSSI
    16. Relationship between NSI and Core NSSI
    17. Relationship between TN-BH Slice Profile and Service Profile
    18. Relationship between TN-BH Slice Profile and TN-BH NSSI
    19. Relationship between NSI and TN-BH NSSI
  4. Verify whether the status from SDN-R is success
  5. Verify whether response code 200 is received from TN for FH, MH & BH
  6. Verify whether response code 200 is received from CN
  7. Verify the asynchronous response from NSSMFs


To check:

Need to check how the Python SDK can be used for automation