ec162e0f56
As our internal QE reported to us, ddt is producing more consistent names of the same tests with different variables then testscenarios. With testscenarios it is something like: foo_tempest_plugin.tests.something.SomeClass.test_foo[id-123456](c1,c2) and with ddt is more similar to tests without scenarios: foo_tempest_plugin.tests.something.SomeClass.test_foo_1[id-123456] Apparently due to this inconsistency results of some tests couldn't be properly reported properly to some tools which we are using downstream. So this patch proposes to remove usage of testscenarios in neutron_tempest_plugin and replace it with ddt where it is needed. Actually ddt was already used in some of the tests here so this will make it also more consistent across the tests in that repo. Also as part of this effort I relalised that in some cases testscenarios where used, tests were running e.g. 2 times but actually variable set to different value in different scenarios were not used at all. So in such case I simply dropped usage of testscenarios and left only one variant of the test to be run. Change-Id: Ieabab4ccaa0e2a365939425dff0c0776839251eb
21 lines
699 B
Plaintext
21 lines
699 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.
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
neutron-lib>=1.25.0 # Apache-2.0
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
netaddr>=0.7.18 # BSD
|
|
os-ken>=0.3.0 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
packaging>=20.4 # Apache-2.0
|
|
paramiko>=2.0.0 # LGPLv2.1+
|
|
tempest>=29.2.0 # Apache-2.0
|
|
tenacity>=3.2.1 # Apache-2.0
|
|
ddt>=1.0.1 # MIT
|
|
testtools>=2.2.0 # MIT
|
|
eventlet!=0.18.3,!=0.20.1,>=0.18.2 # MIT
|
|
debtcollector>=1.2.0 # Apache-2.0
|