Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / 57fa9373563ce798d7a3a3f2e712562506aaa4b2
commit57fa9373563ce798d7a3a3f2e712562506aaa4b2[log] [tgz]
authorA.R Karthick <kramanar@ciena.com>Wed May 24 12:47:03 2017 -0700
committerA.R Karthick <kramanar@ciena.com>Wed May 24 12:49:11 2017 -0700
tree797ff7856fde875eb0a293337ee412c8a22ddfc2
parent51014eff1ed02e55689d1322b98233f589321140 [diff]
Support to enable VOLTHA in cord-tester.
VOLTHA can now be started by cord-tester by specifying voltha_loc in manifest file.
voltha_intf specifies the interface for voltha to listen.
A sample manifest-voltha.json can be modified accordingly before starting cord-tester.
Changed the default olt_type to simulated_olt in volthaTest configuration json.
This would enable testing of voltha tests.
Fix indentation broken in voltha tests earlier.

Change-Id: Ia18b870c83dcb60c15c07f8602579494f32457c9
6 files changed
tree: 797ff7856fde875eb0a293337ee412c8a22ddfc2
  1. .gitignore
  2. COPYRIGHT.txt
  3. Dockerfile.onos-builder
  4. Dockerfile.quagga
  5. Dockerfile.radius
  6. Dockerfile.tester
  7. LICENSE.txt
  8. README.md
  9. Vagrantfile
  10. apply_license.sh
  11. build-onos-docker.sh
  12. build.gradle
  13. buildSrc/
  14. config/
  15. cord-tester-deploy.yml
  16. cord-tester-verify.yml
  17. docs/
  18. gradle/
  19. gradlew
  20. gradlew.bat
  21. libs/
  22. roles/
  23. src/
README.md

cord-tester

CORD Automated Tester Suite

The CORD Automated Tester Suite (CATS) is an extensible end-to-end system test suite targeting CORD PODs. It is typically deployed as one or more Docker containers, either on the CORD POD or adjacent to the POD and interacts with the POD through the PODs interfaces.

Its intended use includes:

  • Regression testing for CORD related component development
  • Acceptance testing of a deployed CORD POD
  • Health-testing of an existing CORD POD (including non-service-impacting and possibly service-impacting tests)

The strength of the CATS will come from the collaboration of the whole CORD/ONOS community, and as such we welcome contributions.

For further information, please browse in the ~/docs directory.