# 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>=3.0.1,<3.1.0 # Apache-2.0

ddt>=1.0.1 # MIT
fixtures>=3.0.0 # Apache-2.0/BSD
stestr>=2.0.0 # Apache-2.0
testscenarios>=0.4 # Apache-2.0/BSD
testtools>=2.2.0 # MIT
coverage!=4.4,>=4.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0

# 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>=3.0.1,<3.1.0 # Apache-2.0

ddt>=1.0.1 # MIT
fixtures>=3.0.0 # Apache-2.0/BSD
stestr>=2.0.0 # Apache-2.0
testscenarios>=0.4 # Apache-2.0/BSD
testtools>=2.2.0 # MIT
coverage!=4.4,>=4.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0
WebTest>=2.0.29 # MIT, for testing with pecan

Add WebTest as a test dependency
Add WebTest as a test dependency

Pecan has made WebTest an optional dependency for testing only [1].
Since it is used for blazar unit testing, we need to add it to the
test-requirements.

The lower version bound is required by requirements-check.
It is (arbitrarily) taken from the Queens' upper-constraints.

[1] https://github.com/pecan/pecan/pull/140

Change-Id: I67b730a21676a8191756effec7e15ab1895e1c95
