Introduction

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 5 typical cases automatically covered to prevent regressions there
  
  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 in ce-bundle
• test will be executed using Firefox as this one has a headless mode
• future: tests will additionally be executed with different browsers (Firefox, Chrome, Safari, Ie, ...) an different OS's (OSX, Unix, Windows, iOs, ...) using hudson slaves