charm-ceph/tests
2015-02-24 10:59:26 +00:00
..
charmhelpers [trivial] charmhelpers sync 2015-02-24 10:59:26 +00:00
00-setup Amulet test fixes: 2014-09-27 18:15:47 +00:00
12-basic-precise-grizzly Add Amulet basic tests 2014-08-26 02:06:25 +00:00
13-basic-precise-havana Add Amulet basic tests 2014-08-26 02:06:25 +00:00
14-basic-precise-icehouse Add Amulet basic tests 2014-08-26 02:06:25 +00:00
15-basic-trusty-icehouse Add Amulet basic tests 2014-08-26 02:06:25 +00:00
basic_deployment.py Sync charm-helpers and fix lint errors. 2014-09-29 20:41:39 +00:00
README Amulet test fixes: 2014-09-27 18:15:47 +00:00

This directory provides Amulet tests that focus on verification of ceph
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