| tag | 26e6e3d958ed7305642df5cc3a58339f6795d600 | |
|---|---|---|
| tagger | Jenkins <do-not-reply@opencord.org> | Fri Jul 26 20:20:30 2019 +0000 |
| object | 9276492f2d14ca4cd445f71b03fff6d51f745bea |
Tagged by CORD Jenkins version-tag job: 2090, for Gerrit patchset: 14796
| commit | 9276492f2d14ca4cd445f71b03fff6d51f745bea | [log] [tgz] |
|---|---|---|
| author | Kailash <kailash@onlab.us> | Thu Jul 25 08:21:39 2019 -0700 |
| committer | Kailash <kailash@onlab.us> | Fri Jul 26 13:05:44 2019 -0700 |
| tree | 427266af2ca126a3b23fd611e710eda3612d203e | |
| parent | 8b6cc4d31812206869474b3bd9daffc7f5f7fc98 [diff] |
VOL-1790 test framework and sanity test commit Change-Id: I66b8f93927232c13c62f6c0459f1f7afacf100e6
#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:
##Prerequisites
voltctl - a command line tool to access VOLTHA. Reference - voltctlkubectl - a command line tool to access your Kubernetes Clusers. Reference - kubectlvoltctl and kubectl should be configured to your system under test prior to any test executionsDirectory 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
Download voltha-system-tests
git clone https://gerrit.opencord.org/voltha-system-testsCreate test virtual-environment
cd voltha-system-tests/source setup_venv.shRunning Test-Suites
robot --exclude notready sanity.robotThis test execution will generate three report files (output.xml, report.html, log.html). View the report.html page to analyze the results.