Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / a0925323817bf1b55efe4ea1a2ea20f3b40ef0bb
commita0925323817bf1b55efe4ea1a2ea20f3b40ef0bb[log] [tgz]
authorA R Karthick <kramanar@ciena.com>Wed Jul 27 10:27:55 2016 -0700
committerKarthick Ramanarayanan <kramanar@ciena.com>Wed Jul 27 10:50:55 2016 -0700
treebf8d3079d53db97cd5cc662dea894a2b68b2ffcc
parent3184d06034ea04e692f9a3103b6235190b84aa3b [diff]
Test: Reorg. cord-tester code in general.
Change test cases to use olt configuration as appropriate when switch isn't running in the test container.
Remove olt multitable config and fold into olt_config.
Rename subscriberMultiTable to cordSubscriber test.
Change the eval script to reflect the new changes/design in cord tester.

Change-Id: I4849b32603ac790a31ba7cfb65b3f87a7c9e2076
(cherry picked from commit b03cecd58829437d3bfe53d3dd6cbc8c5edeb19e)
15 files changed
tree: bf8d3079d53db97cd5cc662dea894a2b68b2ffcc
  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.