Hi, 2013/11/14 11:32:41 David Kranz <dkr...@redhat.com> wrote: 「Re: [openstack-dev] [qa] Tracking development of scenario tests」 > On 11/13/2013 07:35 PM, Christopher Yeoh wrote: > > > On Thu, Nov 14, 2013 at 9:54 AM, David Kranz <dkr...@redhat.com> wrote: > > > It was clear at the summit that there is a pressing need for > more scenario tests. A number of folks have volunteered to participate so we > need a way to track progress and avoid duplication. We have not had great > satisfaction using either bugs or blueprints, so Sean and I are proposing a > more "self-service" approach and process: > > 1. Developer checks in the zeroth version of a scenario test as > work in progress. It contains a description of the test, and possibly > work items. This will "claim" the area of the proposed scenario to avoid > duplication and allow others to comment through gerrit. > > > > I don't know how well it maps for scenario testing, but I think the > spreadsheet approach for the API tests has worked pretty well. Makes the > breakdown of large chunks of work more manageable > > > Chris > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > Yeah, I thought about that. It works well when the spec is a collection of > independent one-liners like it is for apis but scenarios are more involved. I > also like the idea of putting the spec together with the code and the > commenting utility of gerrit. We thought it was worth a try.
I think etherpads is useful for the first step. Of course, more systematic/automatic approach as David said is better. I have no idea for now, though.. Best Regards, -- Masayuki Igawa
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
