Uploaded image for project: 'Magnolia DX Core'
  1. Magnolia DX Core
  2. MGNLEE-501

Proper EE UI-test cleanup

    XMLWordPrintable

Details

    • Task
    • Resolution: Duplicate
    • Neutral
    • None
    • None
    • None
    • None
    • 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

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mmuehlebach Michael Mühlebach
                Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR