I personally like Option #1 as an additional goal is to make it easy for developers to also run the functional tests with 'tox -efunctional'. And also run the functional tests as part of a normal tox run.
On Mon, Jan 11, 2016 at 6:54 AM, Serge Kovaleff <[email protected]> wrote: > Option 3 - to concentrate on Tempest tests > https://review.openstack.org/#/c/253982/ > > Cheers, > Serge Kovaleff > http://www.mirantis.com > cell: +38 (063) 83-155-70 > > On Mon, Jan 11, 2016 at 4:49 PM, Serge Kovaleff <[email protected]> > wrote: > >> Hi All, >> >> Last week I had a noble goal to write "one-more" functional test in >> Ironic. >> I did find a folder "func" but it was empty. >> >> Friends helped me to find a WIP patch >> https://review.openstack.org/#/c/235612/ >> >> and here comes the question of this email: what approach we would like to >> implement: >> Option 1 - write infrastructure code that starts/configure/stops the >> services >> Option 2 - rely on installed DevStack and run the tests over it >> >> Both options have their Cons and Pros. Both options are implemented >> across the OpenStack umbrella. >> Option 1 - Glance, Nova, the patch above >> Option 2 - HEAT and my favorite at the moment. >> >> Any ideas? >> >> Cheers, >> Serge Kovaleff >> http://www.mirantis.com >> cell: +38 (063) 83-155-70 >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
