[MGNLEE-501] Proper EE UI-test cleanup Created: 07/Aug/17  Updated: 12/Jan/18  Resolved: 12/Jan/18

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLEE-500 Adapt to changes from MGNLCE-86 Closed
duplicate
is duplicated by MGNLEE-515 Adapt EE ui tests to use the new dock... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Improve QA setup
Story Points: 21

 Description   

After the CE UI-tests have been cleaned-up we should do the same for the EE UI-tests.

Part of that cleanup effort should be at least:

  • Remove AbstractMagnoliaEEUITest.setDefaultDriverTimeout()
  • Clean up errors from previous point: solve issues after setting implicitlyWait to zero
    • Use proper wait untils/assert eventually in dynamic contexts
  • Remove AbstractMagnoliaEEUITest.appIsLoaded() and replace inappropriate uses (see MGNLCE-88)
  • Extract conditions and locators into the base classes in the CE bundle

General Tip: Write and optimize the tests in a way so that they are not EE specific. Meaning they should not rely on the Abstract EE UI Test class, they should not have EE only helper classes, etc


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