Update on this:

The tools for checking for and adding UUIDs has been completed and reviewed.


A new patch has been sent up that adds UUIDs to all tests


Note that after discussion with the openstack-qa team the decorator has
changed to be of the form


Once the second patch lands you will most certainly need to rebase your work
and include ids in all new tests. When refactoring tests, please preserve the
id value so that various projects (Defcore, Refstack, Rally) can track the 
location of tests for capability testing.

Chris Hoge
Interop Engineer
OpenStack Foundation

> On Feb 22, 2015, at 11:47 PM, Chris Hoge <chris+openstack...@openstack.org> 
> wrote:
> Once the gate settles down this week I’ll be sending up a major 
> “big bang” patch to Tempest that will tag all of the tests with unique
> identifiers, implementing this spec: 
> https://github.com/openstack/qa-specs/blob/master/specs/meta-data-and-uuid-for-tests.rst
> The work in progress is here, and includes a change to the gate that
> every test developer should be aware of.
> https://review.openstack.org/#/c/157273/
> All tests will now require a UUID metadata identifier, generated from the
> uuid.uuid4 function. The form of the identifier is a decorator like:
> @test.meta(uuid='12345678-1234-5678-1234-567812345678')
> To aid in hacking rules, the @test.meta decorator must be directly before the
> function definition and after the @test.services decorator, which itself
> must appear after all other decorators.
> The gate will now require that every test have a uuid that is indeed
> unique.
> This work is meant to give a stable point of reference to tests that will
> persist through test refactoring and moving.
> Thanks,
> Chris Hoge
> Interop Engineer
> OpenStack Foundation

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to