yahoo-eng-team team mailing list archive

[OpenStack Infra <1585209@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/322282
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b450a03282665aa8da4190d47421aecbfc9afb59
Submitter: Jenkins
Branch:    master

commit b450a03282665aa8da4190d47421aecbfc9afb59
Author: jlopezgu <juan.pablo.lopez.gutierrez@xxxxxxxxx>
Date:   Fri May 27 12:11:43 2016 -0500

    Improved table deletion efficiency
    
    Volumes and instances integration tests deleted and validated entities
    one row at a time, now they are able to delete and validate multiple
    rows at a time.
    
    Change-Id: I7f8fdc7e0ccefdd0f6d71f9f92c8a2aefeec8d54
    Closes-bug: #1585209


** Changed in: horizon
       Status: Fix Committed => Fix Released

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

Title:
  In integration tests table-level deletion is used in an inefficient
  way

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  First, even when one entity is deleted from a table, first it is
  marked then 'Delete <entities>' table-level button is clicked, while
  row-level action could be used for that, omitting 'click checkbox'
  phase.

  Second, when multiple entities are deleted, they are still deleted by
  one (using table-level delete), while it would be faster to first
  select all entities, then click 'Delete <entities>' one time and wait
  until each of them is deleted.

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