charm-neutron-gateway/tests
2015-09-15 20:43:41 +00:00
..
charmhelpers [corey.bryant,r=trivial] Sync charm-helpers to pick up Liberty support. 2015-08-18 13:34:35 -04:00
00-setup update makefile, update amulet test targets, update readme 2015-08-22 04:58:53 +00:00
014-basic-precise-icehouse update amulet test re: quantum-gateway rename 2015-06-25 17:58:14 +00:00
015-basic-trusty-icehouse update amulet test re: quantum-gateway rename 2015-06-25 17:58:14 +00:00
016-basic-trusty-juno update amulet test re: quantum-gateway rename 2015-06-25 17:58:14 +00:00
017-basic-trusty-kilo Enable and fix kilo amulet tests. 2015-07-12 02:39:11 +00:00
019-basic-vivid-kilo update makefile, update amulet test targets, update readme 2015-08-22 04:58:53 +00:00
020-basic-trusty-liberty update tests for liberty, misc test updates for kilo 2015-09-15 20:43:41 +00:00
021-basic-wily-liberty update tests for liberty, misc test updates for kilo 2015-09-15 20:43:41 +00:00
050-basic-trusty-icehouse-git [corey.bryant,trivial] Add icehouse git amulet tests back with new branches. 2015-07-09 18:16:49 +00:00
051-basic-trusty-juno-git update amulet test re: quantum-gateway rename 2015-06-25 17:58:14 +00:00
052-basic-trusty-kilo-git [corey.bryant,trivial] Add basic-trusty-kilo-git amulet tests. 2015-07-08 13:32:23 -04:00
basic_deployment.py update tests for liberty, misc test updates for kilo 2015-09-15 20:43:41 +00:00
README update makefile, update amulet test targets, update readme 2015-08-22 04:58:53 +00:00
tests.yaml update makefile, update amulet test targets, update readme 2015-08-22 04:58:53 +00:00

This directory provides Amulet tests that focus on verification of
quantum-gateway deployments.

test_* methods are called in lexical sort order, although each individual test
should be idempotent, and expected to pass regardless of run order.

Test name convention to ensure desired test order:
    1xx service and endpoint checks
    2xx relation checks
    3xx config checks
    4xx functional checks
    9xx restarts and other final checks

In order to run tests, you'll need charm-tools installed (in addition to
juju, of course):
    sudo add-apt-repository ppa:juju/stable
    sudo apt-get update
    sudo apt-get install charm-tools

If you use a web proxy server to access the web, you'll need to set the
AMULET_HTTP_PROXY environment variable to the http URL of the proxy server.

The following examples demonstrate different ways that tests can be executed.
All examples are run from the charm's root directory.

  * To run all tests (starting with 00-setup):

      make test

  * To run a specific test module (or modules):

      juju test -v -p AMULET_HTTP_PROXY 15-basic-trusty-icehouse

  * To run a specific test module (or modules), and keep the environment
    deployed after a failure:

      juju test --set-e -v -p AMULET_HTTP_PROXY 15-basic-trusty-icehouse

  * To re-run a test module against an already deployed environment (one
    that was deployed by a previous call to 'juju test --set-e'):

      ./tests/15-basic-trusty-icehouse

For debugging and test development purposes, all code should be idempotent.
In other words, the code should have the ability to be re-run without changing
the results beyond the initial run.  This enables editing and re-running of a
test module against an already deployed environment, as described above.

Manual debugging tips:

  * Set the following env vars before using the OpenStack CLI as admin:
      export OS_AUTH_URL=http://`juju-deployer -f keystone 2>&1 | tail -n 1`:5000/v2.0
      export OS_TENANT_NAME=admin
      export OS_USERNAME=admin
      export OS_PASSWORD=openstack
      export OS_REGION_NAME=RegionOne

  * Set the following env vars before using the OpenStack CLI as demoUser:
      export OS_AUTH_URL=http://`juju-deployer -f keystone 2>&1 | tail -n 1`:5000/v2.0
      export OS_TENANT_NAME=demoTenant
      export OS_USERNAME=demoUser
      export OS_PASSWORD=password
      export OS_REGION_NAME=RegionOne