[openstack-dev] [qa][neutron] Moving network api test development to Neutron repo

Salvatore Orlando sorlando at nicira.com
Tue Mar 17 21:22:50 UTC 2015

With the API tests being now available in the neutron repository - and
being actively developed, I would also mandate in reviews that API tests
are provided in lieu of the usual unit tests which at the end of the day do
what the API tests are supposed to do.

This will provide better validation, and perhaps might finally allow us to
tear down the unit test non-sense we had so far.
It's with great shame that I must admit I introduce it as a quick way to
test all plugins in Folsom. But I never expected that contributors would
start building on that.

Hopefullly we could start having unit tests which do what unit tests are
supposed to do - white-box testing methods to provide maximum coverage and
validate their behaviour with different input values.


On 17 March 2015 at 22:04, Maru Newby <marun at redhat.com> wrote:

> tl;dr; As per a discussion in Paris [1], development of Neutron's
> API tests is moving from the Tempest repo to the Neutron repo.
> If you are developing API tests for Neutron in Tempest, please be
> advised that, effective immediately, your efforts should be
> directed towards the Neutron repo.
> The current set of Neutron API tests in Tempest has been
> copied (along with supporting infrastructure) to
> neutron/tests/tempest [1].  Tests in this path are run as part of
> the neutron-dsvm-api job, which will shortly be gating [2].  Test
> changes that previously targeted the tempest/api/network path in
> the Tempest repo should target neutron/tests/tempest/network/api
> in the Neutron repo until further notice.
> Automatic conversion from a Tempest change to a Neutron change is
> possible:
>  - cd [path to neutron repo]
>  - ./tools/copy_api_tests_from_tempest.sh [path to tempest working
> directory]
> As per the Tempest guidelines for test removal [3], the tests
> currently in Tempest will remain in Tempest and continue to run
> as part of the existing jobs until we can target tests in the
> Neutron repo against stable branches and enable the use of the
> in-repo tests by defcore/refstack.
> Finally, guidelines for API test development in the Neutron repo are
> in the works and will be proposed shortly.  The guidelines will
> define policy intended to protect against backwards compatible
> changes to our API.
> Thanks,
> Maru
> 1:
> https://etherpad.openstack.org/p/kilo-crossproject-move-func-tests-to-projects
> 2: https://github.com/openstack/neutron/tree/master/neutron/tests/tempest
> 3: https://review.openstack.org/#/c/164886
> 4: https://wiki.openstack.org/wiki/QA/Tempest-test-removal
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150317/6585d506/attachment.html>

More information about the OpenStack-dev mailing list