Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / f3e0a9fed35c026d7bb120cea493a0546043f5bd
commitf3e0a9fed35c026d7bb120cea493a0546043f5bd[log] [tgz]
authorKailash Khalasi <kailash@onlab.us>Tue Sep 18 13:43:42 2018 -0700
committerKailash Khalasi <kailash@onlab.us>Tue Sep 18 14:52:55 2018 -0700
tree1976deae1ec6aa945316cc0d11b1811b14dc9de6
parent422d1ab8b840fbebbea766296b4f10c4f52a306f [diff]
combining test cases in attworkflow scenario

Change-Id: I0264a111ef8221c07781c44b770811263a4e9b41
2 files changed
tree: 1976deae1ec6aa945316cc0d11b1811b14dc9de6
  1. .gitignore
  2. .gitreview
  3. COPYRIGHT.txt
  4. Dockerfile.onos-builder
  5. Dockerfile.quagga
  6. Dockerfile.tester
  7. Jenkinsfile-attworkflow-build
  8. Jenkinsfile-attworkflow-test
  9. Jenkinsfile-rcordlite-control-plane
  10. Jenkinsfile-rcordlite-topdown
  11. Jenkinsfile-rcordlite-topdown-build
  12. Jenkinsfile-rcordlite-topdown-test
  13. Jenkinsfile-rcordlite-zerotouch
  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.