yahoo-eng-team team mailing list archive

[Akihiro Motoki <1272979@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Even if -c option is not specified to run_tests.sh, unit tests are invoked through coverage command. This makes our unit tests slower.
It is better that coverage is not used unless -c option is specified.

The following is my result on a VM. Test without coverage command is 4
or 5 times faster.

[with coverage command]
horizon: Ran 101 tests in 40.904s
openstack_dashboard: Ran 800 tests in 132.817s

[without coverage command]
horizon: Ran 101 tests in 7.988s
openstack_dashboard: Ran 800 tests in 28.900s

** Affects: horizon
     Importance: Undecided
     Assignee: Akihiro Motoki (amotoki)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1272979

Title:
  coverage is always enabled in run_tests.sh

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  Even if -c option is not specified to run_tests.sh, unit tests are invoked through coverage command. This makes our unit tests slower.
  It is better that coverage is not used unless -c option is specified.

  The following is my result on a VM. Test without coverage command is 4
  or 5 times faster.

  [with coverage command]
  horizon: Ran 101 tests in 40.904s
  openstack_dashboard: Ran 800 tests in 132.817s

  [without coverage command]
  horizon: Ran 101 tests in 7.988s
  openstack_dashboard: Ran 800 tests in 28.900s

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1272979/+subscriptions