According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Iee69eae0043a401eb355a1fcb957879904882e85
As the db manage script will be run primarily in
production enviroments as a means to cleanup old
data. True functional tests are needed to verify
that it does not falsely delete valid information
and that it properly removes the needed informaion
This is the start of any functional tests that are
needed for our cmd support scripts.
Change-Id: Ib6c9309c4ee95d10e124869a31590cfe983e13ec
Alters tox.ini to use testr rather than nosetests.
Also, adds documentation on how to use tox to run a
single functional test class.
Change-Id: I1333ead397f338ee3da3d81b0e1de8e93283a2b5
Closes-Bug: #1490747
Testr pumps out a lot of output to the screen even
with successful tests. Other OpenStack projects
solve this by modifying their testr config to force
stdout and stderr capture similar to other testing
frameworks. For this change, I have copied how
Nova handles this.
Change-Id: Ie6fb60585a632e09fef068f768c6b6fde10017f0
Added tests for secret create (single and two-phase), order
create, and versioning to run in the devstack gate.
These should both provide a base for additional tempest-based
tests and also ensure that future CRs won't regress basic
Barbican functionality.
Added skip to version tests until blueprint fix-version-api
has been implemented.
Change-Id: Ib1d6bb3a2251c21b9d7d647687d0ac30ad52e4c9