yahoo-eng-team team mailing list archive

[Tomáš Nováčik <tnovacik@xxxxxxxxx>]

Public bug reported:

It is not possible right now to run horizon selenium integration tests
concurently.

This request emerged in [0]. Because of following reasons(quoting Timur
Sufiev):

I guess the whole point of running tests as more than 2 users is the
ability to run concurrently more than 1 suite of integration tests
against the single devstack instance (different browsers, different
Linux versions on the horizon host) - the exact combinations are perhaps
will be left to the people setting up the environment, nevertheless
upstream gate is not the only place that would benefit from these tests.

For example in Mirantis Openstack we need to run integration tests both
for Horizon being deployed on CentOS and on Ubuntu. The ability to use a
single devstack node for both sets of test could lower the requirements
to the hardware on the gate (though I'm not sure yet that it will be
done this exact way). It is known that concurrent running of 2 test
suites as one user on one devstack host could pose a problem, at least
from Keystone side (tokens handling).

Proposed solution:

I suggest to take advantage of nosetests argument --processes [1] and in
each separate process create two types of users (admin and demo-like)
using this patch [2].

[0] https://review.openstack.org/#/c/115092
[1] http://nose.readthedocs.org/en/latest/plugins/multiprocess.html#cmdoption--processes
[2] https://review.openstack.org/#/c/143027/

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
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/1406128

Title:
  running integration tests concurently

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  It is not possible right now to run horizon selenium integration tests
  concurently.

  This request emerged in [0]. Because of following reasons(quoting
  Timur Sufiev):

  I guess the whole point of running tests as more than 2 users is the
  ability to run concurrently more than 1 suite of integration tests
  against the single devstack instance (different browsers, different
  Linux versions on the horizon host) - the exact combinations are
  perhaps will be left to the people setting up the environment,
  nevertheless upstream gate is not the only place that would benefit
  from these tests.

  For example in Mirantis Openstack we need to run integration tests
  both for Horizon being deployed on CentOS and on Ubuntu. The ability
  to use a single devstack node for both sets of test could lower the
  requirements to the hardware on the gate (though I'm not sure yet that
  it will be done this exact way). It is known that concurrent running
  of 2 test suites as one user on one devstack host could pose a
  problem, at least from Keystone side (tokens handling).

  Proposed solution:

  I suggest to take advantage of nosetests argument --processes [1] and
  in each separate process create two types of users (admin and demo-
  like) using this patch [2].

  [0] https://review.openstack.org/#/c/115092
  [1] http://nose.readthedocs.org/en/latest/plugins/multiprocess.html#cmdoption--processes
  [2] https://review.openstack.org/#/c/143027/

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