Gitiles
Code Review Sign In
gerrit.lfbroadband.org / voltha-system-tests / 5b80f672a77a13ca87169f3b82bd18151d3c5494
commit5b80f672a77a13ca87169f3b82bd18151d3c5494[log] [tgz]
authorAndy Bavier <andy@opennetworking.org>Tue Aug 27 10:31:53 2019 -0700
committerAndy Bavier <andy@opennetworking.org>Tue Aug 27 10:31:53 2019 -0700
tree2568e92db4f8de59d0ef6acd167a781f1a5addcc
parent9b50efc60eee5558d047c3302b2c315184f81f57 [diff]
Use pip instead of pip3 due to errors installing robotframework-kafkalibrary

Change-Id: I36e3675d34d052c8d2ae10df7563b49c081da800
1 file changed
tree: 2568e92db4f8de59d0ef6acd167a781f1a5addcc
  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