zaqar/test-requirements.txt
Fei Long Wang d3f69d93c0 Using os-testr to get better report
As a wrapper of testr, os-testr can provide subunit-trace for output
which is useful for debug.

Change-Id: I99f3a01ea85cbbf2b9a970b75bff19c63f7e44eb
2017-02-08 22:45:40 +00:00

41 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.
# Metrics and style
hacking<0.11,>=0.10.0
# Packaging
mock>=2.0 # BSD
# Backends
redis>=2.10.0 # MIT
pymongo!=3.1,>=3.0.2 # Apache-2.0
python-swiftclient>=3.2.0 # Apache-2.0
websocket-client>=0.32.0 # LGPLv2+
# Unit testing
coverage>=4.0 # Apache-2.0
ddt>=1.0.1 # MIT
fixtures>=3.0.0 # Apache-2.0/BSD
python-subunit>=0.0.18 # Apache-2.0/BSD
testscenarios>=0.4 # Apache-2.0/BSD
testrepository>=0.0.18 # Apache-2.0/BSD
testtools>=1.4.0 # MIT
oslo.db>=4.15.0 # Apache-2.0
testresources>=0.2.4 # Apache-2.0/BSD
os-testr>=0.8.0 # Apache-2.0
# Documentation
sphinx!=1.3b1,<1.4,>=1.2.1 # BSD
oslosphinx>=4.7.0 # Apache-2.0
openstackdocstheme>=1.5.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
reno>=1.8.0 # Apache-2.0
os-api-ref>=1.0.0 # Apache-2.0
# Tempest
tempest>=12.1.0 # Apache-2.0
#OSprofiler
osprofiler>=1.4.0 # Apache-2.0