[MGNLCE-15] Improve UI-Test waitUntils for asserting vanished objects Created: 08/Dec/15  Updated: 04/Jan/16  Resolved: 29/Dec/15

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Basel 24
Story Points: 2

 Description   

Selenium has no explicit functionality to assert that an object is gone. Our test just work with the inverted result from a findElement. But this means we always wait until the default timeout has passed.

The standard approach is to set the implicit waiting time to something quite small (like 50ms) and reset it to the default afterwards.

pmundt has this change already on a seperate branch with jenkins jobs.

Part of this ticket is to:

  • Apply this approach at every applicable place (specially all ee tests)
  • Integrate everything to master
  • Remove the unneeded jenkins jobs

Generated at Mon Feb 12 00:05:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.