charm-neutron-api/tests
2015-04-23 15:51:27 +01:00
..
charmhelpers [gnuoy,trivial] Pre-release charmhelper sync 2015-04-23 15:51:27 +01:00
00-setup Add amulet tests 2015-02-17 07:10:15 +00:00
014-basic-precise-icehouse auto rename amulet tests 2015-04-16 21:35:58 +00:00
015-basic-trusty-icehouse auto rename amulet tests 2015-04-16 21:35:58 +00:00
016-basic-trusty-juno auto rename amulet tests 2015-04-16 21:35:58 +00:00
017-basic-trusty-kilo amulet tests - enable trusty-kilo and vivid-kilo 2015-04-19 04:03:54 +00:00
018-basic-utopic-juno auto add amulet tests for supported releases 2015-04-16 21:36:14 +00:00
019-basic-vivid-kilo amulet test - update for trusty-kilo variations; disable vivid-kilo test, pending juju support. 2015-04-19 14:43:03 +00:00
050-basic-trusty-icehouse-git auto rename amulet tests 2015-04-16 21:35:58 +00:00
051-basic-trusty-juno-git auto rename amulet tests 2015-04-16 21:35:58 +00:00
basic_deployment.py amulet test - adjust openstack series logic re: things to do with kilo and later 2015-04-20 20:03:43 +00:00
README Add amulet tests 2015-02-17 07:10:15 +00:00

This directory provides Amulet tests that focus on verification of
neutron-api deployments.

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