Jump to: navigation, search

Difference between revisions of "QA"

(Project Team Definition)
Line 155: Line 155:
| Source code
| Source code
| http://git.openstack.org/cgit/openstack/os-performance-tools
| http://git.openstack.org/cgit/openstack/os-performance-tools
=== Patrole ===
{| border="1" cellpadding="2"
| Source code
| http://git.openstack.org/cgit/openstack/patrole
| Bug tracker
| https://bugs.launchpad.net/patrole

Revision as of 19:57, 10 March 2018

QA is an official OpenStack project team.

Project Team Definition

Official Title: OpenStack Quality Assurance

PTL: Ghanshyam Mann (gmann)

Mission Statement:
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 release cycle.


The OpenStack QA project team is made of multiple projects which each run independently towards the goals of the project team. Each project maintains a separate core team based on who provides reviews in those projects.

For the purposes of voting on QA Project Team activities, anyone that's core on any of the projects gets a vote.


Source code http://git.openstack.org/cgit/openstack/tempest/
Bug tracker https://bugs.launchpad.net/tempest
Feature tracker https://blueprints.launchpad.net/tempest
Developer Documentation http://docs.openstack.org/developer/tempest/

Test removal procedure:


Tempest-lib (Deprecated)

Source code http://git.openstack.org/cgit/openstack/tempest-lib/
Bug tracker https://bugs.launchpad.net/tempest
Feature tracker https://blueprints.launchpad.net/tempest
Developer Documentation http://docs.openstack.org/developer/tempest-lib/

Tempest -> Tempest-lib migration

To migrate a module from tempest into tempest-lib follow these instructions: tempest-lib-migration

Tempest Plugin Cookiecutter

Source code http://git.openstack.org/cgit/openstack/tempest-plugin-cookiecutter
Bug tracker https://bugs.launchpad.net/tempest


For more information see: Grenade

Source code http://git.openstack.org/cgit/openstack-dev/grenade/
Bug tracker https://bugs.launchpad.net/grenade


For more information see: DevStack

Documentation http://docs.openstack.org/developer/devstack/
GitHub https://github.com/openstack-dev/devstack
Bug tracker https://bugs.launchpad.net//devstack

Devstack Plugin Cookiecutter

Source code http://git.openstack.org/cgit/openstack-dev/devstack-plugin-cookiecutter
Bug tracker https://bugs.launchpad.net/devstack

Devstack Vagrant

Source code http://git.openstack.org/cgit/openstack-dev/devstack-vagrant
Bug tracker https://bugs.launchpad.net/devstack


Source code http://git.openstack.org/cgit/openstack-dev/hacking
Bug tracker https://bugs.launchpad.net/hacking
Documentation http://docs.openstack.org/developer/hacking


Source code http://git.openstack.org/cgit/openstack-dev/bashate


Source code http://git.openstack.org/cgit/openstack/os-testr
Bug tracker https://bugs.launchpad.net/os-testr
Documentation http://docs.openstack.org/developer/os-testr


Source code http://git.openstack.org/cgit/openstack/openstack-health
Bug tracker https://bugs.launchpad.net/openstack-health


Source code http://git.openstack.org/cgit/openstack/stackviz


Source code http://git.openstack.org/cgit/openstack/os-performance-tools


Source code http://git.openstack.org/cgit/openstack/patrole
Bug tracker https://bugs.launchpad.net/patrole

Project liaisons

To make cross project communication easier and fill gaps in domain expertise between projects and QA (bidirectionally) each project designates a liaison for handling integration issues. See QAProjectLiaisons.

Feature proposals

To propose a feature to any of the QA projects you first need to file a spec in qa-specs. The entire process is outlined here: qa-specs-process

Pushing Releases

The process for pushing project releases is documented here: QA/releases


IRC Channel: #openstack-qa on freenode


The QA project team has a weekly IRC meeting, for more details see: