ee6a257f58
With a fix in wsgi-intercept 1.7.0 we can properly use the PlacementFixture as a context manager to simulate when placement is configured for a given operation. This allows us to remove the ugly stub that one of the tests in here had to rely on. While in here, the CastAsCall fixture is removed since we shouldn't rely on that in these tests where we're trying to simulate the user experience. Change-Id: I2074b45126b839ea6307a8740364393e9dddd50b
30 lines
933 B
Plaintext
30 lines
933 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
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
ddt>=1.0.1 # MIT
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0.0 # BSD
|
|
mox3>=0.20.0 # Apache-2.0
|
|
psycopg2>=2.6.2 # LGPL/ZPL
|
|
PyMySQL>=0.7.6 # MIT License
|
|
python-barbicanclient>=4.5.2 # Apache-2.0
|
|
python-ironicclient>=2.3.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
osprofiler>=1.4.0 # Apache-2.0
|
|
testresources>=2.0.0 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
bandit>=1.1.0 # Apache-2.0
|
|
gabbi>=1.35.0 # Apache-2.0
|
|
|
|
# vmwareapi driver specific dependencies
|
|
oslo.vmware>=2.17.0 # Apache-2.0
|
|
|
|
# placement functional tests
|
|
wsgi-intercept>=1.7.0 # MIT License
|