Hello Neutron team, >From the "Testing Requirements" section, Tempest is mentioned as a requirement. Does that mean all the thirdparty vendors' system should run all the tests in Tempest?
It might not make perfect sense to test image API for changes in the neutron code. So can we define some subset of tests that are relevant to neutron (e.g. tempest.api.network, tempest.scenario.test_network_* ). Also, some plugins may not implement full set of APIs defined by Neutron, (for example. Vendor X hasn't supported floating IP API). What should be the acceptance criteria for the API compatibility? Thanks, Tomoe On Mon, Nov 18, 2013 at 10:59 PM, Russell Bryant <rbry...@redhat.com> wrote: > On 11/18/2013 08:42 AM, Kyle Mestery (kmestery) wrote: > > Yong, if you read Mark's proposal closely, the third party tests will > only run when the specific third party code is touched, or when the Jenkins > user submits code. > > > > On Nov 17, 2013, at 11:50 PM, Yongsheng Gong <gong...@unitedstack.com> > wrote: > > > >> For third party testing, I am afraid these tests will make the patch > merge process much longer since each patch, which even has nothing to do > with the specific plugins, will triggers the unwanted third party testing > jobs. > > And note that if it's not gating, we do not necessarily have to wait for > every third party system to report in before merging the patch. > > -- > Russell Bryant > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
