Gitiles
Code Review Sign In
gerrit.opencord.org / cord-tester / bdb1ec46f212f12ce2785e0b47513774c5f4669e
commitbdb1ec46f212f12ce2785e0b47513774c5f4669e[log] [tgz]
authorThangavelu K S <kthangav@partner.ciena.com>Thu Feb 23 19:51:42 2017 +0000
committerChetan Gaonker <chgaonke@partner.ciena.com>Thu Feb 23 12:21:36 2017 -0800
treeb45da6be5b88bed9efd3bde6aad2f232ab6b4bdf
parente4660f582d9594d9299a9962da7133eb6ec3daf6 [diff]
cord-vtn-test:
   Adding around 90 new test case templates
   with detailed steps to validate
   cord vtn in context of openstack neutron, nova ,
   keystone services, vtn config and flows .

   This will validate multiple scenarios for cordvtn synching networks created
   on neutron and flows created & installed.
   CORD tester will be using Python neutron client APIs, nova client APIs
   and Keystone API's extensively.

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