Gitiles
Code Review Sign In
gerrit.lfbroadband.org / voltha-system-tests / baed17e78973fe475d0bc97eb7bd5bcbb11f986c
commitbaed17e78973fe475d0bc97eb7bd5bcbb11f986c[log] [tgz]
authorSuchitra Vemuri <suchitra@opennetworking.org>Fri Aug 30 15:22:09 2019 -0700
committerSuchitra Vemuri <suchitra@opennetworking.org>Fri Aug 30 15:22:09 2019 -0700
treee0a971a001b38fc1ea89d144bfb63a08eba72039
parent65cd65f50bb0268ef2169ea4dd4a1211193ac461 [diff]
Jenkins file for voltha test job

Change-Id: I173e174c59f6da6de58ccfdec9abb847f36a2473
2 files changed
tree: e0a971a001b38fc1ea89d144bfb63a08eba72039
  1. .gitreview
  2. Jenkinsfile-voltha-build
  3. Jenkinsfile-voltha-test
  4. Makefile
  5. README.md
  6. VERSION
  7. libraries/
  8. setup_venv.sh
  9. tests/
  10. 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