Re: [openstack-dev] [tempest] UUID Tagging Requirement and Big Bang Patch

2015-02-27 Thread Chris Hoge
This work has landed. New tests will now be gated against existence of an 
idempotent_id.
If you have open submissions to Tempest there’s a good possibility you’ll have 
to rebase.

-Chris

 On Feb 26, 2015, at 2:30 PM, Chris Hoge chris+openstack...@openstack.org 
 wrote:
 
 Update on this:
 
 The tools for checking for and adding UUIDs has been completed and reviewed.
 
 https://review.openstack.org/#/c/157273 
 https://review.openstack.org/#/c/157273
 
 A new patch has been sent up that adds UUIDs to all tests
 
 https://review.openstack.org/#/c/159633 
 https://review.openstack.org/#/c/159633
 
 Note that after discussion with the openstack-qa team the decorator has
 changed to be of the form
 
 @test.idempotent_id('12345678-1234-5678-1234-123456789abc’)
 
 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 
 actual
 location of tests for capability testing.
 
 Thanks,
 Chris Hoge
 Interop Engineer
 OpenStack Foundation
 
 On Feb 22, 2015, at 11:47 PM, Chris Hoge chris+openstack...@openstack.org 
 mailto: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
  
 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
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [tempest] UUID Tagging Requirement and Big Bang Patch

2015-02-26 Thread Chris Hoge
Update on this:

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

https://review.openstack.org/#/c/157273 
https://review.openstack.org/#/c/157273

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

https://review.openstack.org/#/c/159633 
https://review.openstack.org/#/c/159633

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

@test.idempotent_id('12345678-1234-5678-1234-123456789abc’)

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 
actual
location of tests for capability testing.

Thanks,
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
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [tempest] UUID Tagging Requirement and Big Bang Patch

2015-02-22 Thread Chris Hoge
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
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev