yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67487
[Bug 1177924] Re: Use testr instead of nose as the unittest runner.
fixed I53ef4a116996a772cf1f3abc2eb0ad60047322d5
** Changed in: swift
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1177924
Title:
Use testr instead of nose as the unittest runner.
Status in Ceilometer:
Fix Released
Status in Cinder:
Fix Released
Status in django-openstack-auth:
New
Status in Glance:
Fix Released
Status in OpenStack Dashboard (Horizon):
Triaged
Status in OpenStack Identity (keystone):
Fix Released
Status in manila-ui:
New
Status in python-ceilometerclient:
Fix Released
Status in python-cinderclient:
Fix Released
Status in python-heatclient:
Fix Released
Status in python-keystoneclient:
Fix Released
Status in OpenStack Object Storage (swift):
Fix Released
Status in OpenStack DBaaS (Trove):
Triaged
Bug description:
We want to start using testr as our test runner instead of nose so
that we can start running tests in parallel. For the projects that
have switched we have seen improvements to test speed and quality.
As part of getting set for that, we need to start using testtools and
fixtures so provide the plumbing and test isolation needed for
automatic parallelization. The work can be done piecemeal - with
testtools and fixtures being added first, and then tox/run_tests being
ported to us testr/subunit instead of nose.
This work was semi tracked during Grizzly with this
https://blueprints.launchpad.net/openstack-ci/+spec/grizzly-testtools
blueprint. I am opening this bug so that we can track migration to
testr on a per project basis.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1177924/+subscriptions