...

Here's the typical testing pyramid - it clearly shows that UI tests will not replace any other tests (manual tests or Acceptance (Integration) tests).

UI Tests

Goals

...

Have few typical cases automatically covered to prevent regressions there.

1. Basic Content App test (use Contacts App as it's a simple example)
   
   • navigate to Contact App, open a contact in a tab
   • edit (modify), save, close
   • verify tree is updated
     
     
2. Bookmarking (use Contacts App again)
   
   • open new default subapp
   • navigate to opened default sub app
   • open new non-default subapp - verify default subapp is also opened
   • navigate to opened non-default sub app
     
     
3. Activation
   
   • verify basic activation works - no workflow
   • LATER (when workflow is ready): verify activation with workflow
     
     
4. Test Pages App

• • Test basic Page editing


1. assure accessing a subapp via LocationChange (past URL into browser) opens the right subapp and the default sub app of it's parent app
2. tbd
3. tbd
4. tbd
5. tbd
• have it automated
collect practical experience with Selenium

Design

• test will go into magnolia-integration-test/uitests in ce-bundle
• test will be executed using Firefox as this one has a headless mode

Outlook

• Execute tests with with future: tests will additionally be executed with different browsers (Firefox, Chrome, Safari, Ie, ...) an different OS's (OSX, Unix, Windows, iOs, ...) using hudson slaves

...