Cloned from launchpad blueprint https://blueprints.launchpad.net/tripleo/+spec/automated-ui-testing.
At the moment, upstream CI only tests for lint errors, and runs our unittests. We'd like to add more integration tests for tripleo-ui to the CI pipeline. This will include a selenium-based approach. This allows us to simulate a browser by using a headless browser when running in CI, and we can detect a lot more problems than we ever could with just unittesting.
This new work should be integrated into the upcoming tempest plugin for tripleo-ui for ease of reporting
Specification URL (additional information):
*** This bug has been marked as a duplicate of bug 1545275 ***