← Back to branch summary

~openstack-charmers/charms/trusty/lxd/trunk

« back to all changes in this revision

Viewing changes to tests/tests.yaml

  • Committer: Ryan Beisner
  • Date: 2016-07-20 21:54:09 UTC
  • Revision ID: ryan.beisner@canonical.com-20160720215409-ik6re3ktrlwlwolb
Use bundletester for amulet test execution

Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.

Rename amulet tests inline with gate-*, dev-* and dfs-*
naming standards.

Update README to refer to functional testing section of the charm
guide.

Change-Id: I892dfad152eff14d7e67313197c61dacc4a9eca2

Show diffs side-by-side

added added

removed removed

Lines of Context:
tests/tests.yaml
1
 
bootstrap: true
2
 
reset: false
3
 
virtualenv: true
4
 
makefile:
5
 
    - lint
6
 
    - test
7
 
sources:
8
 
    - ppa:juju/stable
9
 
packages:
10
 
    - amulet
11
 
    - distro-info-data
12
 
    - python-ceilometerclient
13
 
    - python-cinderclient
14
 
    - python-distro-info
15
 
    - python-glanceclient
16
 
    - python-heatclient
17
 
    - python-keystoneclient
18
 
    - python-neutronclient
19
 
    - python-novaclient
20
 
    - python-pika
21
 
    - python-swiftclient
 
1
# Bootstrap the model if necessary.
 
2
bootstrap: True
 
3
# Re-use bootstrap node instead of destroying/re-bootstrapping.
 
4
reset: True
 
5
# Use tox/requirements to drive the venv instead of bundletester's venv feature.
 
6
virtualenv: False
 
7
# Leave makefile empty, otherwise unit/lint tests will rerun ahead of amulet.
 
8
makefile: []
 
9
# Do not specify juju PPA sources.  Juju is presumed to be pre-installed
 
10
# and configured in all test runner environments.
 
11
#sources:
 
12
# Do not specify or rely on system packages.
 
13
#packages:
 
14
# Do not specify python packages here.  Use test-requirements.txt
 
15
# and tox instead.  ie. The venv is constructed before bundletester
 
16
# is invoked.
 
17
#python-packages: