[openstack-dev] [qa] Tracking development of scenario tests

Christopher Yeoh cbkyeoh at gmail.com
Thu Nov 14 00:35:50 UTC 2013

On Thu, Nov 14, 2013 at 9:54 AM, David Kranz <dkranz at 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131114/2a874aad/attachment.html>

More information about the OpenStack-dev mailing list