yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #48821
[Bug 1564405] [NEW] Integration tests don't actually wait until table row is deleted
Public bug reported:
Usually it goes unnoticed because objects are deleted at the end of a
test (cleanUp phase) - and the deletion manages to finish before the
next test is launched, but when a dependent entities A<-B are deleted in
order, sometimes not waiting for B to delete leads to failure while
deleting A (a good example here is Volume <- Volumes Snapshot).
This was caused by too broad exception clause here
https://github.com/openstack/horizon/blob/2015.1.0rc2/openstack_dashboard/test/integration_tests/basewebobject.py#L42
(in reality exception was raised due to absence of .is_displayed()
method in RowRegion, we had to invoke element.src_elem.is_displayed() in
that case).
** Affects: horizon
Importance: High
Assignee: Timur Sufiev (tsufiev-x)
Status: In Progress
** Changed in: horizon
Importance: Undecided => High
** Changed in: horizon
Milestone: None => newton-1
--
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/1564405
Title:
Integration tests don't actually wait until table row is deleted
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
Usually it goes unnoticed because objects are deleted at the end of a
test (cleanUp phase) - and the deletion manages to finish before the
next test is launched, but when a dependent entities A<-B are deleted
in order, sometimes not waiting for B to delete leads to failure while
deleting A (a good example here is Volume <- Volumes Snapshot).
This was caused by too broad exception clause here
https://github.com/openstack/horizon/blob/2015.1.0rc2/openstack_dashboard/test/integration_tests/basewebobject.py#L42
(in reality exception was raised due to absence of .is_displayed()
method in RowRegion, we had to invoke element.src_elem.is_displayed()
in that case).
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1564405/+subscriptions
Follow ups