neutron/neutron/tests/tempest
Kevin Benton 4e8cc68349 Increment revision numbers on object changes
This adds the logic to increment the revision numbers
for objects whenever there are changes and it exposes
the revision number via a field in the API.

This is handled with a new default service plugin that
subscribes to DB events and bumps revision numbers for
any objects that were modified.

It also handles the logic for bumping the revision number
of a parent in a relationship where the children aren't
top-level neutron objects that would be tracked individually.
This is accomplished with a 'revises_on_change' attribute
on the child models that the service plugin will use to
find the parent and bump its revision.

API tests are included to test the revision numbers
added to each standard attribute enabled object.

Partially-Implements: bp/push-notifications
Change-Id: I476d3e03c8ee763cc4be6d679fe9f501eb3a19b5
2016-07-27 12:01:55 -07:00
..
api Increment revision numbers on object changes 2016-07-27 12:01:55 -07:00
common Copy tempest.common.tempest_fixtures in to Neutron 2016-03-09 19:01:35 -05:00
scenario QoSTest: skip if qos extension is not available 2016-07-15 15:01:45 +09:00
services Revisit (add|remove)_subports request body 2016-07-21 15:41:40 +00:00
README.rst Use tempest plugin interface 2016-04-14 15:19:14 +02:00
__init__.py Initial copy of api tests from tempest 2015-03-09 21:24:55 +00:00
config.py tests: validate sorting and pagination for networks 2016-05-24 09:17:25 +00:00
exceptions.py Switch to using in-tree tempest lib 2016-02-26 14:00:11 +00:00
plugin.py tempest: enable hacking rule checks 2016-04-18 23:47:33 +02:00

README.rst

WARNING

The files under this path were copied from tempest as part of the move of the api tests, and they will be removed as required over time to minimize the dependency on the tempest testing framework. While it exists, only neutron.tests.tempest.api and neutron.tests.retargetable should be importing files from this path. neutron.tests.tempest.config uses the global cfg.CONF instance and importing it outside of the api tests has the potential to break Neutron's use of cfg.CONF.