Context 

Main aim: We need a better „UI tests framework“ in order to make it „easier / simpler“ to write and maintain UI tests quicker.

After some discussion the „Group of Interest for QA/Testing“ has decided  to proceed with selenium driver based tests. 

In order to reach the main aim, we want to create an API following the Page Objects pattern. This allows to write the UI tests by utilizing the page objects API (instead of using the selenium API) leading to tests with less code, which are easier to read, understand and maintain.

 Preliminary studies

Back in the days, Michi Mühlebach started with the creation of Page objects. Rico did a first follow-up with DEV-1199. (See Page object extraction initiative too).

Acceptance criteria & Scope

• Define minimal API which is sufficient for the given functional test
• Implement the API.
• Provide tests to test the implemented API.
• Write a new UI test for the given scenario by utilizing the new API

It is sufficient, if the (new) Page Objects API enables UI tests for Magnolia 6.1 and higher only. No need to support tests required for m-5.7.x branch.

Do not change / alter existing classes, but create new classes / interfaces. Create a new package somewhere (most likely within ce/magnolia-integration-tests/tests for the time being).

Ideally, the public API is completely free of selenium types. (me thinks) (???).

Scenario to test

Given paige opens the Contacts app:
When she creates the contact Goethe.
Then Goethe contact exists.

paige: Is editing (and creating) content; has the role editor.