Unit tests generally will all be executed, and measuring them will
skew the overall coverage numbers. Thus, I'm excluding the unit_tests
folder.
Change-Id: Iec5e57b305615d4d3fe87cb46b771d92d14a5195
This technique was borrowed from the tox "cover" environment in
openstack/nova's tox.ini. This leverages the fact that stestr lets
you override the python executable via the PYTHON environment
variable. Doing this allows us to easily generate coverage for our
unit tests.
An important caveat is that this does not provide any coverage for
tests via zaza, amulet, etc. It is purely focused on the unit tests.
Note that this replaces the previous .coveragerc; coverage
configuration is instead pulled from tox.ini.
Change-Id: I2a14d3a3b0215aa637bc18e780d1ad765c796daa
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I2068cc2748021157c6d5e4f4b6cbd85790dd11b7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Misc updates for rocky:
- Switch default smoke test to bionic-rocky
- Resync charm helpers
The change for this charm is minimal as it directly uses
ceph-common. The cinder charm actually deals with installation
of the required python-rados/rbd libraries for the ceph
integration.
Change-Id: Ic2ee4b845ab604d80b7e27492f522d57f9463af1
As of pip 10.0, --allow-unverified is not permitted.
Use of the flag in this repo was previously used to force
installation of python-apt to accommodate certain unit tests.
The unverified package, python-apt, is no longer necessary
for test execution.
Related-Bug: #1760720
Change-Id: I9516fa288f9b04c8822c707e8649916a3f8e0fc6
Also sync charm-helpers
This change requires the following charm-helpers change
to land first:
- https://github.com/juju/charm-helpers/pull/32
Change-Id: I2c33e25e14ad49d65f5fc7eb000830086cf829c1
- Turn on Zesty-Ocata Amulet test definitions.
- Standardize test-requirements.txt
- Sync charm helpers for various fixes
Change-Id: I4ddc4d75eb86210abb073a92d8ed217a3f39fa55
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
Change-Id: Idf45ef0e0587e6874e29145c7ce1109be7cc4e50
All OpenStack Charms now contain identical tox.ini files,
not to be modified or made unique within each charm repo.
This is to ensure consistency across charm repos in tox
target naming, approach and purpose, also giving the
charm dev and test experience additional consistency.
Also create empty dirs with .keep files where necessary.
Some classic charms have actions and/or lib dirs, and some
do not. In all classic charms, flake will now check those
dirs to ensure lint coverage of existing or future content.
Change-Id: I671077fbafb38bd4d2005fb2236bec416f79593f
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.
Also remove brittle auth conf checks which are failing at
cinder-ceph master. Even without those explicit checks, if auth
fails, functional tests will still fail and block.
Change-Id: I91e638f98f70c7098f089c7e60c1181632b39222
The new release of charm-tools no longer ships the charm
command; update minimum version requirement and switch
to using charm-proof instead, unblocking current pep8
failures across all charms.
Also pin the version of requests to 2.6.0 until theblues
(indirect dependency of charm-tools) sort out its
requirements versioning.
Change-Id: I9ffc23d111d35833dc44fc33a27111bed55b6577