← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1177924] Re: Use testr instead of nose as the unittest runner.

 

** Changed in: python-heatclient
       Status: Fix Committed => Fix Released

** Changed in: python-heatclient
    Milestone: v0.2.3 => None

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to 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 OpenStack Image Registry and Delivery Service (Glance):
  New
Status in OpenStack Dashboard (Horizon):
  Triaged
Status in OpenStack Identity (Keystone):
  Confirmed
Status in Python client library for Ceilometer:
  Fix Committed
Status in Python client library for Cinder:
  Fix Committed
Status in Python client library for heat:
  Fix Released
Status in Python client library for Keystone:
  Fix Released
Status in OpenStack Object Storage (Swift):
  New
Status in Trove - Database as a Service:
  New

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