
os-testr has moved over to use stestr instead of testr. While this is usually compaible with existing settings, there is a warning that is emitted when .stestr.conf is not present. It is usually able to fall back to parsing the .testr.conf file, but to be more correct and to prevent future problems we should update the config. Change-Id: I929f75d069f20b8cfa8af4e0712883e91a54dc4f
34 lines
1.0 KiB
Plaintext
34 lines
1.0 KiB
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
|
|
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
|
|
# oslo.log can't be a runtime dep because it would cause a circular dependency,
|
|
# but we can optionally make use of it so we want to have it installed in our
|
|
# test environment.
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
|
|
# when we can require tox>= 1.4, this can go into tox.ini:
|
|
# [testenv:cover]
|
|
# deps = {[testenv]deps} coverage
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
|
|
# this is required for the sphinx extension
|
|
sphinx!=1.6.6,!=1.6.7,>=1.6.2 # BSD
|
|
|
|
# mocking framework
|
|
mock>=2.0.0 # BSD
|
|
requests_mock>=1.5.0 # Apache-2.0
|
|
|
|
# Bandit security code scanner
|
|
bandit>=1.1.0 # Apache-2.0
|
|
|
|
reno>=2.5.0 # Apache-2.0
|