Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / b50f559ae837fd754eba1a055550504767c86dd2
commitb50f559ae837fd754eba1a055550504767c86dd2[log] [tgz]
authorA R Karthick <kramanar@ciena.com>Tue Jul 26 12:19:29 2016 -0700
committerA R Karthick <kramanar@ciena.com>Tue Jul 26 12:19:29 2016 -0700
treefaf46ad4fcb93827e4684ebcdb19ab54f6aa95c6
parent006429b3fc37e0657116bb3ed5b496a362d95abd [diff]
Test: Cleanup the test container interfaces with --olt option.
Also make the olt configuration similar to the podd (atleast for single node) by
configuring the test container ports to reside on br-int ovs bridge.

Change-Id: I6afd20d2e58532b252b9dc614d0d16f27b590578
3 files changed
tree: faf46ad4fcb93827e4684ebcdb19ab54f6aa95c6
  1. .gitignore
  2. .gitreview
  3. COPYRIGHT.txt
  4. Dockerfile.quagga
  5. Dockerfile.radius
  6. Dockerfile.tester
  7. LICENSE.txt
  8. README.md
  9. Vagrantfile
  10. apply_license.sh
  11. build.gradle
  12. docs/
  13. gradle/
  14. gradlew
  15. gradlew.bat
  16. libs/
  17. settings.gradle
  18. 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.