openstack-qa-team team mailing list archive

[David Kranz <david.kranz@xxxxxxxxxx>]

Sorry for the late posting. Here are some things to discuss today.

 -David

Discuss priorities for Tempest, recorded in 
http://etherpad.openstack.org/TempestPriorities


1. Get tempest gating online

Make sure that smoke tests are not duplicated, test basic positive 
functionality, and not skipped.
Get the gating job online in Jenkins.
File bugs for the tests that need to have their resource use cut back.

2. Address the lack of cohesion between OpenStack development activity 
and Tempest.

Introduce the notion of QA states for a blueprint:
    * QA resource identified
    * Test plan discussion with the blueprint author
    * Code is feature complete and ready for testing
    * unit tests complete
    * functional (tempest) tests complete
    * documented

Make sure the dev teams know to include the QA resource in any 
discussions. They should be part of the team for that feature.
Add a QA Assignee to the blueprint template.

Request that the PTLs (or some designee) send a weekly email to the QA 
list (main list?) identifying which features are ready to start 
functional and integration testing and which will soon be ready, as well 
as who to contact about issues that come up in writing tests for each 
feature.

3. Start testing Folsom features. Many are already checked in. A partial 
list is in the etherpad.

4. Get stress testing online

There are a number of tempest clients that are not included in the 
current stress tests.
Round them out and start running stress tests continuously.


5. Do what we can to get companies using OpenStack to do more of their 
QA work "in the open"

If we increased the visibility of some kind of QA structure, perhaps 
others would find it attractive to plug their testing into that much as 
happens with development. Of course we would have to create that 
structure first.