Page History
...
Here's the typical testing pyramid - it clearly shows that UI tests will not replace any other tests (manual tests or Acceptance/Integration tests) but will complete our test setup.
UI Tests
For now we'll We use Selenium for testing our ui. Test The UITest will be part of magnolia-integration-test/tests and use its test-webapp & test-public-webapp (much as the integration tests do). UITests are only triggered if you specify the corresponding profile (uitest). As specifying a profile no longer invokes the default profile (jetty6-standalone) you have to pass this one as well.
In short, use the following command to locally run the uitests
Code Block | ||||
---|---|---|---|---|
| ||||
..../magnolia-integration-tests/tests mvn clean install -P uitest,jetty6-standalone |
Goals
Have few typical cases automatically covered to prevent regressions there.
...
Creating those tests is tracked under
Jira | ||||
---|---|---|---|---|
|
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
...