# 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>=1.1.0,<1.2.0 # Apache-2.0

fixtures>=3.0.0 # Apache-2.0/BSD
testscenarios>=0.4 # Apache-2.0/BSD
stestr>=2.1.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

# mocking framework
mock>=3.0.0 # BSD
requests_mock>=1.5.0 # Apache-2.0

# Bandit security code scanner
bandit>=1.1.0,<1.6.0 # Apache-2.0
