Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / 92a0e5a8353f40a5550f3e606b5bb1e485d88acb
commit92a0e5a8353f40a5550f3e606b5bb1e485d88acb[log] [tgz]
authorA R Karthick <kramanar@ciena.com>Wed Jun 22 17:11:05 2016 -0700
committerA.R Karthick <kramanar@ciena.com>Thu Jun 23 15:13:02 2016 -0700
tree1fa4a784d0f50130a307a1c7e207f825096d2d9d
parente0f33fa1bc088c91e0ce40c17622cbb31760ffa1 [diff]
Test: Now cord-test.py setup would start and provision the test container to run nosetests from the container.
If one wants to dynamically launch the test container for running cord-tester tests,
they can still do the cord-test.py run to execute the tests.

Change-Id: I0df8604398c3369385b9e4ffeb590ce89565498d
1 file changed
tree: 1fa4a784d0f50130a307a1c7e207f825096d2d9d
  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.