Hi Flavio, On Tue, Dec 8, 2015 at 9:52 PM, Flavio Percoco <fla...@redhat.com> wrote: > > > Oh, I meant ocasionally. Whenever a missing test for an API is found, > it'd be easy enough for the implementer to sohw up at the meeting and > bring it up.
>From my experience as a Tempest reviewer, I'd say that most newly added tests are *not* submitted by Tempest regular contributors. I assume (wrongly ?) that it's mostly people from the actual projects (e.g glance) who are interested in adding new Tempest tests to test a feature recently implemented. Put differently, I don't think it's part of Tempest core team/community to add new tests. We mostly provide a framework and guidance these days. But, reading this thread, I don"t know what to suggest. As a Tempest reviewer I won't start a new ML thread or send a message to a PTL each time I see a new test being added...I assume the patch author to know what he is doing, I can't keep on with what's going on in each and every project. Also, a test can be quickly removed if it is latter on deemed not so useful. Jordan
__________________________________________________________________________ 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
