summaryrefslogtreecommitdiff
path: root/tempest/api/network/test_extensions.py
Commit message (Collapse)AuthorAgeFilesLines
* Adding description for testcases - network part1zhufl2020-07-271-1/+1
| | | | | | | | | | | | | | | When Tempest is used in customer site, often we are required to provide a testcase list including testcase names and descriptions. Now no this kind of doc is available, so we can add descriptions with the format of doc string for every testcase, so later we can generata such a testcase description list. There are hundreds of testcases missing descriptions, so we can add them gradually, and limit the modified files in one patch for the convenience of reviewing. Change-Id: Id3e49c09116c08b6a017b6bb9d016bb31cad9fcd partially-implements: blueprint testcase-description
* Move test decorators to commonAndrea Frittoli2017-08-231-3/+3
| | | | | | | | | services and extension decorators are based on CONF and needed by Tempest only, so moving them to tempest.common. Since a few plugnis use them today, use debtcollector to avoid breaking all dependencies. Change-Id: Ibd52153d00b8e60fb8c89e38d94e358ddc787251
* Move the `attr` decorator from test.py to tempest/libJordan Pittier2017-04-141-1/+1
| | | | | | | | I think it's a good idea to move all utility decorators into tempest/lib/decorators.py. This patch does that for the `attr` decorator. Change-Id: Iaafbb112b6eee458089cc49918359a8a8d0485e2
* Switch to decorators.idempotent_id on networkKen'ichi Ohmichi2017-02-041-1/+2
| | | | | | | | So many modules are using test.idempotent_id and this is for switching to decorators.idempotent_id on network. Change-Id: I2735d04dfbd5d48e87894457f2fc1172edf4da44 Related-Bug: #1616913
* Correct a misleading in docstringTianbiao Qi2016-09-291-3/+3
| | | | | | | | Testcase in test_extensions gets api-extensions from section of [network-feature-enabled] instead of [network]. This is correcting it and making the docstring more explicit. Change-Id: I1e25169cc7819e1571bb75522ea3ab5035459bb1
* deprecate use of tenant in configsSean Dague2016-04-061-1/+1
| | | | | | | | | | OpenStack has settled (a very long time ago) on project to represent the container which has users. We should make tempest configs always use project versions of these names. This deprecates the old tenant versions of these names, and makes project version the prefered option. Change-Id: Ied68c0326cf891a4e6eb3db51dc5f43241e4b8d2
* Split out Neutron extensions clientKen'ichi Ohmichi2016-01-271-2/+3
| | | | | | | | Splitting out a extensions client for Neutron. Partially implements blueprint consistent-service-method-names Change-Id: I49b30eac4d7db0b06a3b0946158e542801cf4e75
* Fix H404/405 violations for api tests(2/3)Ken'ichi Ohmichi2015-11-191-4/+1
| | | | | | | | There is a lot of H404/405 violations in Tempest now, and that leads difficult to migrate the code to tempest-lib or the other projects' repos. This patch fixes these violations for api tests of network. Change-Id: I50c59abe3fe40346602e2c07d9b0b1b20a3a471d
* remove service-type from neutron extension listSean Dague2015-09-021-1/+1
| | | | | | | | | | service-type as an extension is only exposed if neutron advanced services are enabled because neutron extensions are unlike nova extensions and aren't directly loaded things, but interfaces that plugins register that they support. Change-Id: I6c38bace04070d71b74fa2b18866b3976f2a8524 Closes-Bug: #1491333
* Add extension alias for test_list_show_extensionsTakeaki Matsumoto2015-08-111-1/+2
| | | | | | | | Some API tests use metering, dvr, and service-type extensions, but test_list_show_extensions doesn't check them. This add checking them. Change-Id: Ibf21a2aa41ea51a0ffda4c32075bd26472af8d2e
* Neutron: Remove get_namespace from API extensionsSean M. Collins2015-06-101-1/+0
| | | | | | | | Based on the conversation on the ML. http://lists.openstack.org/pipermail/openstack-dev/2015-June/066219.html Change-Id: I95a0aba75d10d15a94b0eeaed80a8f7a22b85625
* Split resource_setup for network testsRohan Kanade2015-03-271-4/+0
| | | | | | | | | Split up the resource_setup method for all the network tests, as per the latest spec. Partially-implements bp:resource-cleanup Change-Id: If96a154cfe65dd3d18ff6b1e1943ccfb1db7300e
* Add UUIDs to all tempest tests and gate checkChris Hoge2015-02-261-0/+1
| | | | | | | | | | | | | Adds uuid4 as a decorator of the form: @test.idempotent_id('12345678-1234-1234-1234-123456789abc') to every test in the Tempest tree. Includes a gate check to ensure the existence and uniqueness of the ids. Modify check tool to ignore Tempest unit tests. Change-Id: I19e3c7dd555a3ea09d585fb9091c357a300e6559 Co-Authored-By: Sergey Slipushenko <sslypushenko@mirantis.com> Implements: bp test-uuid
* Drop the legacy and un-used _interfaceAndrea Frittoli2015-02-121-1/+0
| | | | | | | | | | We used to run JSON and XML tests. XML has been dropped now, but still in the code there are remains of the logic to switch between JSON and XML. Cleaning them up. Partially-implements: bp/resource-cleanup Change-Id: I39ecfbd99861136a6a2adc3ce56bfdbba96d5c9b
* Change neutron client methods to return one value and update testsDavid Kranz2014-12-181-2/+2
| | | | | | | | | | | | | Also removed redundant ok checks in javelin.py and put in a work-around for the existing assumption that all client 'list_' methods have the same signature. It was necessary to change the mocked network calls in the unit tests. Since the mocked status is never referenced, it was just removed. Partially implements: blueprint clients-return-one-value Change-Id: I76de07e984f13e3eec4977a4d823d1ef367e8f46
* part 2 of delete xmlSean Dague2014-11-251-4/+0
| | | | | | part of removal of xml from tempest Change-Id: I4218f5db2d6ff42dd208c2c06e4bf2c7baea2f6b
* Migrate network API tests to resource_* fixturesAndrea Frittoli2014-09-181-2/+2
| | | | | | Partially-implements bp resource-cleanup Change-Id: I455c372f7356343f4398f69255c6150c3521b953
* Move API response success check to Neutron clientRohan Kanade2014-08-261-4/+2
| | | | | | | | | * Move all API response success validation from Neutron API tests to Neutron base/json/xml clients Partially Implements blueprint: client-checks-success Change-Id: I784e9b610f64564861e94d20c6200d1e6915e7f7
* make testing neutron api extensions optionalYoshihiro Kaneko2014-02-051-0/+2
| | | | | | | | When the Neutron API extension that test case needs is unsupported by Neutron plugin running, the test case will be skipped. Change-Id: Ie3b0f94ea084076ccc10d6a141c9120bf9900395 Closes-Bug: #1270244
* Remove vim headersMasayuki Igawa2014-01-201-2/+0
| | | | | | | | | | | | We don't need to have the vim headers in each source files. We can set it in our vimrc file instead. Also if set incorrectly, gate (pep8 check) will catch the mistakes. More discussions: http://lists.openstack.org/pipermail/openstack-dev/2013-October/017353.html Change-Id: I43703e2289212389c7841f44691ae7849ed1f505 Closes-Bug: #1229324
* Merge "Fix failures when l3_agent_scheduler ext is not available"Jenkins2013-12-181-4/+6
|\
| * Fix failures when l3_agent_scheduler ext is not availablearmando-migliaccio2013-12-131-4/+6
| | | | | | | | | | | | | | | | | | Some plugins do not support the L3 agent scheduler extension. Therefore, make the tests that rely on it dependent on whether this is actually available in the plugin under test. Change-Id: I3154b646677379a34465c6826b71d4ad72c471a2 Closes-bug: #1231152
* | Refactor network clientEugene Nikanorov2013-12-171-1/+1
|/ | | | | | | | | | | | | | | | This patch implements the following steps in network client refactoring 1) Automatically 'generated' list_, show_, delete_ methods for most of the resources 2) XML and JSon client implementations inherit common base 3) Every list method now supports filters This change allow to remove existing list_, show_ and delete_ methods for simple resources from both clients. Some tests were fixed to simplify mapping between client method name and resulting URI (example: list_floatingips instead of list_floating_ips) Change-Id: I0eb46f8e3d90809dbfc54d4a250cd6aecfdc2c3b
* Added test to check list/show extensions-neutronNayna Patel2013-09-231-0/+79
Added a test script 'test_extensions.py' to api/networks to verify if list/show of extensions is successful in neutron. Also added supporting methods 'list_extensions' and 'show_extension_details' in network client for XML and JSON interfaces. Implements blueprint: quantum-test-l2-abstraction Change-Id: Ie939a3e1302060489b579baf2cd3f7023efbeb7d