Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / a013a274ab85a0baaa77ebdc86557fe7b55f740b
commita013a274ab85a0baaa77ebdc86557fe7b55f740b[log] [tgz]
authorA R Karthick <kramanar@ciena.com>Tue Aug 16 16:40:19 2016 -0700
committerA R Karthick <kramanar@ciena.com>Tue Aug 16 16:42:33 2016 -0700
tree6b8db3134cb4202834efa6b93c41c2217e3363c0
parentb5b46c68155ba84092e88e41701edbfdf6acfbaa [diff]
Test: Changes to cordSubscriber to delete ovs groups before the test.
This is done through a remote rpc or local as appropriate.
This also seems to make the single channel N subscriber tests receive packets after join as OVS seems flaky otherwise.
Support for cord-test.py run to execute tests with container name setup with:
cord-test.py setup --olt --start-switch
option.

Change-Id: Ifca43e9b7e76bb231ed8ad84b6971d985b66b9e1
4 files changed
tree: 6b8db3134cb4202834efa6b93c41c2217e3363c0
  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.