Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / 992665b2757870da7892d2171f557118ecc89f10
commit992665b2757870da7892d2171f557118ecc89f10[log] [tgz]
authorWei-Yu Chen <aweimeow.tw@gmail.com>Thu Jan 17 10:21:32 2019 -0800
committerMatteo Scandolo <teo@opennetworking.org>Thu Jan 17 18:27:40 2019 +0000
tree1752695dc36f945c4f85f7a76233cf2924558b4e
parent4200e57073c1c3b9b92608c2a21dde169a8b8d08 [diff]
Added M-CORD infrastruture CNI and Clean up steps

Change-Id: If99e94000ff36499fa7435f555e3bb3e45d54d7f
1 file changed
tree: 1752695dc36f945c4f85f7a76233cf2924558b4e
  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.