Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-system-tests / 1a871bfe76a42db85eba849d0d99f2dc059cb0d2
commit1a871bfe76a42db85eba849d0d99f2dc059cb0d2[log] [tgz]
authorKailash <kailash@onlab.us>Mon Aug 05 14:20:02 2019 -0700
committerKailash <kailash@onlab.us>Mon Aug 05 14:27:51 2019 -0700
tree38413542453d1a3855edd0b25b990b1a6880cc59
parentce30501785fef1f2a758256c686c548325c2fb3a [diff]
minor test fixes

Change-Id: I71184a2d6aa49ee8101e39988bb8d6fccc7a0634
2 files changed
tree: 38413542453d1a3855edd0b25b990b1a6880cc59
  1. .gitreview
  2. Makefile
  3. README.md
  4. VERSION
  5. libraries/
  6. setup_venv.sh
  7. tests/
  8. 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