Ann, You are correct. We WILL NOT develop negative tests anymore by hand. We will take a "generative" approach in the future. I will update the etherpad to reflect this
Regards On Mon, Dec 23, 2013 at 5:12 AM, Anna Kamyshnikova < akamyshnik...@mirantis.com> wrote: > Hello! > > I'm working on creating tests in tempest according to this etherpad page > https://etherpad.openstack.org/p/icehouse-summit-qa-neutron. > > Here is mentioned that we should be add negative tests, for example, for > floating ips, but as I understand (according to comment to > https://bugs.launchpad.net/bugs/1262113) negative tests will be added > automatically. In this case, is work on such tests as > - Negative: create a floating ip specifying a non public network > - Negative: create a floating ip specifying a floating ip address out of > the external network subnet range > > - Negative: create a floating ip specifying a floating ip address that is > in use > > - Negative: create / update a floating ip address specifying an invalid > internal port > > - Negative: create / update a floating ip address specifying an internal > port with no ip address > > - Negative: create / update a floating ip with an internal port with > multiple ip addresses, specifying an invalid > > - Negative create /assciate a floating ip with an internal port with > multiple ip addresses, when the ip address > > - Negative: delete an invalid floating ip > > - Negative: show non existing floating ip > needed or not? > > Ann. > > > On Mon, Dec 23, 2013 at 2:56 PM, Sean Dague <s...@dague.net> wrote: > >> Please take this to a public list >> >> On 12/23/2013 03:42 AM, Anna Kamyshnikova wrote: >> > Hello! >> > >> > I'm working on creating tests in tempest according to this etherpad >> > page https://etherpad.openstack.org/p/icehouse-summit-qa-neutron. >> > >> > Here is mentioned that we should be add negative tests, for example, for >> > floating ips, but as I understand (according to your comment >> > to https://bugs.launchpad.net/bugs/1262113) negative tests will be >> added >> > automatically. In this case, is work on such tests as >> > - Negative: create a floating ip specifying a non public network >> > - Negative: create a floating ip specifying a floating ip address out of >> > the external network subnet range >> > >> > - Negative: create a floating ip specifying a floating ip address that >> > is in use >> > >> > - Negative: create / update a floating ip address specifying an invalid >> > internal port >> > >> > - Negative: create / update a floating ip address specifying an internal >> > port with no ip address >> > >> > - Negative: create / update a floating ip with an internal port with >> > multiple ip addresses, specifying an invalid >> > >> > - Negative create /assciate a floating ip with an internal port with >> > multiple ip addresses, when the ip address >> > >> > - Negative: delete an invalid floating ip >> > >> > - Negative: show non existing floating ip >> > >> > needed or not? >> > >> > Ann. >> >> >> -- >> Sean Dague >> http://dague.net >> >> > > _______________________________________________ > 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
