Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-system-tests / 0e2465cc5730811dd028664c98ada222eca93ab0
commit0e2465cc5730811dd028664c98ada222eca93ab0[log] [tgz]
authorKailash <kailash@onlab.us>Mon Aug 05 09:56:02 2019 -0700
committerKailash Khalasi <kailash@opennetworking.org>Mon Aug 05 17:05:36 2019 +0000
treef979f7514f0e29dc85a58a715af933ae0b771c42
parent528f7c03cb142a58624f9059b3c3822f508201cd [diff]
setting global kubectl voltctl env vars

Change-Id: Ic85343b78feb6b5a32ba42b28106e07732458556
3 files changed
tree: f979f7514f0e29dc85a58a715af933ae0b771c42
  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