Introduction

Here's the typical testing pyramid - it clearly basically shows that UI tests will not replace any other tests (manual tests or Acceptance/Integration tests) but will complete our test setup.

Image Removed

UI Tests

For now we'll use Selenium for testing our ui. Test will be part of magnolia-integration-test and use its test-webapp & test-public-webapp (much as the integration tests do)

Goals

Have few typical cases automatically covered to prevent regressions there.

...

there's different layers of tests and that in lower layers one should have most tests and hence the biggest coverage. On the very top - the manual tests - should be very minimal.

Image Added

• • Test basic Page editing

Tracking

Creating those tests is tracked under 

Next steps

• integrate with ordinary integration tests to re-use it's setup in pom
• merge to master
• re-activate hudson job
• complete once demo-project can be added to test web apps

Outlook

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