Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / f97ee1344208fb9878664bcd0d40d47a89468b91
commitf97ee1344208fb9878664bcd0d40d47a89468b91[log] [tgz]
authorA R Karthick <kramanar@ciena.com>Thu Mar 23 09:48:37 2017 -0700
committerA R Karthick <kramanar@ciena.com>Thu Mar 23 09:48:37 2017 -0700
tree1f93791da9d65c0e83ef46fea602eba5225914db
parent2e99c4727313ac9ecb0c26b57cca4a6b8a717883 [diff]
With --noswitch option to cord-tester run, just create a dummy OVS switch.
This would just allow pipework to provision the test container ports on the OVS switch

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