Gitiles
Code Review Sign In
gerrit.lfbroadband.org / voltha-system-tests / 6f5acb6e898210aeaebc54f07ec638543aba8ae6
commit6f5acb6e898210aeaebc54f07ec638543aba8ae6[log] [tgz]
authorKailash <kailash@onlab.us>Wed Aug 28 14:38:45 2019 -0700
committerKailash <kailash@onlab.us>Wed Aug 28 15:16:07 2019 -0700
tree832bd435db467a47cb130325c4dbfc4df9c59c8d
parentb1753e49684be9020dbe204bed30997250ab46c7 [diff]
creating voltctl and onos test libraries
creating voltha physical pod build JF

Change-Id: I26cb4f15c2f00c0a9bb951e75dcb35cbcd89cea7
6 files changed
tree: 832bd435db467a47cb130325c4dbfc4df9c59c8d
  1. .gitreview
  2. Jenkinsfile-voltha-build
  3. Makefile
  4. README.md
  5. VERSION
  6. libraries/
  7. setup_venv.sh
  8. tests/
  9. variables/
README.md

System-Tests

Automated test-suites to validate the stability/functionality of VOLTHA. Tests that reside in here should be written in Robot Framework and Python.

Intended use includes:

  • Sanity testing
  • Regression testing
  • Acceptance testing
  • Functional testing
  • Scale Testing using BBSIM
  • Failure/Scenario testing

Prerequisites

  • Python Virtual-Env
  • voltctl - a command line tool to access VOLTHA. Reference - voltctl
  • kubectl - a command line tool to access your Kubernetes Clusers. Reference - kubectl
    • voltctl and kubectl should be configured to your system under test prior to any test executions

Directory Structures are as followed:

├── tests
  └── sanity/           // basic tests that should always pass. Will be used as gating-patchsets
  └── functional/       // feature/functionality tests that should be implemented as new features get developed
└── libraries           // shared test keywords (functions) across various test suites
└── variables           // shared variables across various test suites

Getting Started

  1. Download voltha-system-tests

    • git clone https://gerrit.opencord.org/voltha-system-tests

  2. Create test virtual-environment

    • cd voltha-system-tests/
    • source setup_venv.sh

  3. Running Test-Suites

    • Navigate to desired test suite location
    • robot --exclude notready sanity.robot

This test execution will generate three report files (output.xml, report.html, log.html). View the report.html page to analyze the results.

WIP:

  • Containerizing test environment so these tests can be run independent of the system