Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / 7f8c4dd122548761c25da56009414d21ee33cdef
commit7f8c4dd122548761c25da56009414d21ee33cdef[log] [tgz]
authorWei-Yu Chen <aweimeow.tw@gmail.com>Thu Jan 17 15:32:03 2019 -0800
committerMatteo Scandolo <teo@opennetworking.org>Thu Jan 17 23:41:55 2019 +0000
tree475abbf1084eb987e619e3da561effb3d17f76a7
parent82b1a85347c9bc9cfc9b4542893baec1e32218d1 [diff]
Added sleep to avoid helm charts install fail

Change-Id: Ib2bb0a99ec21993deaf17f3de24126b16fce5c03
1 file changed
tree: 475abbf1084eb987e619e3da561effb3d17f76a7
  1. .gitignore
  2. .gitreview
  3. COPYRIGHT.txt
  4. Dockerfile.onos-builder
  5. Dockerfile.quagga
  6. Dockerfile.tester
  7. Jenkinsfile-attworkflow-build
  8. Jenkinsfile-attworkflow-build-released-ver
  9. Jenkinsfile-attworkflow-test
  10. Jenkinsfile-mcord-build
  11. Jenkinsfile-rcordlite-control-plane
  12. Jenkinsfile-rcordlite-topdown-build
  13. Jenkinsfile-rcordlite-topdown-test
  14. Jenkinsfile-rcordlite-zerotouch-build
  15. Jenkinsfile-rcordlite-zerotouch-test
  16. Jenkinsfile/
  17. LICENSE.txt
  18. README.md
  19. VERSION
  20. Vagrantfile
  21. apply_license.sh
  22. build-onos-docker.sh
  23. build.gradle
  24. buildSrc/
  25. config/
  26. cord-tester-deploy.yml
  27. cord-tester-verify.yml
  28. docs/
  29. gradle/
  30. gradlew
  31. gradlew.bat
  32. roles/
  33. 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.