fa12452bbd
For compliance with the Project Testing Interface as described in: https://governance.openstack.org/tc/reference/project-testing-interface.html For more detials information, please refer to: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html Change-Id: I10537cf02d83f127b6932fa3f427043fb267d8b1 Co-Authored-By: Stephen Finucane <sfinucan@redhat.com>
19 lines
555 B
Plaintext
19 lines
555 B
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
|
|
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testtools>=2.3.0 # MIT
|
|
mock>=2.0.0 # BSD
|
|
oslotest>=3.3.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.5.1 # Apache-2.0
|
|
|
|
# Bandit security code scanner
|
|
bandit>=1.1.0 # Apache-2.0
|