Public bug reported:
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.
** Affects: horizon
Importance: Undecided
Status: New
** Tags: integration-tests
** Tags added: integration-tests
--
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):
New
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
