Difference between revisions of "Midokura-third-party-testing"
(Created page with "<!-- ##master-page:HomepageTemplate --> <!-- #format wiki --> <!-- #language en --> = Midokura Third-Party Testing = ---------------------- == Introduction == Midokura...") |
|||
| Line 3: | Line 3: | ||
<!-- #language en --> | <!-- #language en --> | ||
| − | = Midokura Third-Party Testing = | + | <!-- = Midokura Third-Party Testing = |
---------------------- | ---------------------- | ||
| − | + | --> | |
== Introduction == | == Introduction == | ||
| − | Midokura Third-Party Testing (MTPT) runs a set of Tempest tests on every new patch submitted for review to upstream | + | Midokura Third-Party Testing (MTPT) runs a set of Tempest tests on every new patch submitted for review to the upstream master branch of the Openstack Neutron project (currenlty Juno). The patch is tested using the Midonet plugin (currenlty v1.5.0) on a custom devstack environment (we call it midostack) to ensure that the patch does not break the plugin. The Openstack gerrit account name for MTPT is “Midokura CI Bot”. |
Revision as of 10:42, 30 July 2014
Introduction
Midokura Third-Party Testing (MTPT) runs a set of Tempest tests on every new patch submitted for review to the upstream master branch of the Openstack Neutron project (currenlty Juno). The patch is tested using the Midonet plugin (currenlty v1.5.0) on a custom devstack environment (we call it midostack) to ensure that the patch does not break the plugin. The Openstack gerrit account name for MTPT is “Midokura CI Bot”.
Contact Information
For any questions or comments, please contact: mido-openstack-dev@midokura.com
