Open Stack

Just my two cents. I'm not sure calling out test frameworks directly is necessary. I like the more generic terminology before of "tools" since over time our test strategy will likely encompass more than a single test framework. Here's my variation:

"Plan, develop and execute testing tools and strategies to ensure the continuous stability, reliability and quality of OpenStack projects."
________________________________________
From: Patel, Nayna (Cloud Services) [nayna.patel at hp.com]
Sent: Wednesday, July 10, 2013 1:29 PM
To: All Things QA.
Subject: Re: [openstack-qa] Draft QA mission statement

Test cases standards and test framework -- I don't think so :) maybe someone else might want to comment

-----Original Message-----
From: Anita Kuno [mailto:akuno at lavabit.com]
Sent: Wednesday, July 10, 2013 11:10 AM
To: openstack-qa at lists.openstack.org
Subject: Re: [openstack-qa] Draft QA mission statement

Doesn't the definition of standards come from the Technical Committee and the Board?

On 13-07-10 01:26 PM, Patel, Nayna (Cloud Services) wrote:
> I like to revise this Mission Statement as is doesn't talk about improving quality?
> +1 Jay...
>
> Suggestion:
>
> Define and uphold the high quality standards for developing and executing tests in a Continuous Integration release cycles of Openstack and improving the test automation toolsets.
>
> -----Original Message-----
> From: Jay Turner [mailto:jkt at redhat.com]
> Sent: Wednesday, July 10, 2013 5:03 AM
> To: All Things QA.
> Subject: Re: [openstack-qa] Draft QA mission statement
>
> On Tue, 2013-07-09 at 09:24 -0400, Sean Dague wrote:
>> Official Title: OpenStack Quality Assurance
>> PTL: TBD
>> Mission Statement: Develop and maintain tools to ensure the upstream
>> stability and quality of OpenStack, and it's release readiness at any
>> point during the cycle.
>>
>> Trying to not get too far behind the other programs, here's a draft
>> mission statement. Word smithing would be appreciated.
> Maybe I'm being too pedantic, but the statement above is focused
> entirely on the development and maintenance of tools and says nothing
> about the execution of these tools, thus implying another group will
> take that responsibility.  I do not believe that to be the case :-)
>
> "Develop, maintain, and initiate tools and plans to ensure the upstream stability and quality of OpenStack, and its release readiness at any point during the cycle."
>
> - jkt
>
> --
> --*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*
> Jay Turner, Director, Quality Engineering    jkt at redhat.com    Red Hat, Inc.
>
>          "Only two things are infinite, the universe and human
>          stupidity, and I'm not sure about the former." - Albert
> Einstein _______________________________________________
> openstack-qa mailing list
> openstack-qa at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa
>



_______________________________________________
openstack-qa mailing list
openstack-qa at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa

_______________________________________________
openstack-qa mailing list
openstack-qa at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa