Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 23 Next »

Overview

For testing SDN-R with its basic use cases an automated test setup should be used. 

Beside "SDN-R Development integratoin test" there is the "SDN-R Solution integration test"

Related issue:  SDNC-891 - Getting issue details... STATUS

Requirements

  • Simple, run on single ubuntu server 
  • Use Simulators instead of devices
  • Use as far as possible real ONAP server components, if not possible test tools, like VES-test-collector
  • Is compatible with ONAP integration tests setup

Test setup

Environments

Post production test cases

Location

Infrastructure

  • Server "Test VM": sdnr-frankfurt-int 10.20.5.5 provides docker based test environment
  • Static environment for otto
    • oran NTS_Manager 8300 baseport 50000 dir 3gppsim
    • gran NTS_Manager_3GPP 9300 baseport 60000 dir oransim
  • Static environment for frankfurt development build robot
    • oran Robot_NTS_Manager 8200 basport 55000 dir robot-nts-manager 
  • Integration test environment
    • Port ranges 8310 .. 8499, 40000 .. 49999
    • ntssim oran 8310, 40000 .. 40019
  • Static IP assignment in yaml_default network (172.18.0.0/24) with names for /etc/hosts of docker host.
    • 172.18.0.2 sdnrdb
    • 172.18.0.3 sdnr
    • 172.18.0.10 sdnr-0
    • 172.18.0.11 sdnr-1
    • 172.18.0.12 sdnr-2
    • 172.18.0.15 sdnrtestdb

Development (old environment)

  • docker for networking, run containers
  • docker-compose starting a structure
  • bash initialization
  • manual execution of development tests

Test cases

Test case "Inventory"

  • Startup
    • Create docker network
      • a static network setup with static IPs for the containers
      • add name to hosts and use this names
    • start docker - Simulator (e.g. Sim12600 with equipment)
    • start docker - DB
    • start docker - SDNC
  • Test steps
    • mount sim12600
    • Read over the RESTCONF Interface via data-provider the equipment
    • Compare if it is the expected data





  • No labels