Automated UI testing in CI

Registered by Honza Pokorny

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

Blueprint information

Status:
Complete
Approver:
Emilien Macchi
Priority:
High
Drafter:
Honza Pokorny
Direction:
Approved
Assignee:
Honza Pokorny
Definition:
Obsolete
Series goal:
Accepted for stein
Implementation:
Not started
Milestone target:
milestone icon stein-3
Completed by
Juan Antonio Osorio Robles

Related branches

Sprints

Whiteboard

[2018-07-25] (aschultz) moving to Stein
[2018-07-11] patch merged, isn't it "implemented" by now? (aschultz) the spec was merged but I'm not seeing any other patches. Likely needs to be moved to Stein

Gerrit topic: https://review.openstack.org/#/q/topic:bp/automated-ui-testing

Addressed by: https://review.openstack.org/546817
    Add ui automation spec

Gerrit topic: https://review.openstack.org/#q,topic:bp/automated-ui-testing,n,z

Addressed by: https://review.openstack.org/575730
    Add basic project structure

Gerrit topic: https://review.openstack.org/#q,topic:selenium-ci,n,z

Addressed by: https://review.openstack.org/607323
    Add option to install chrome when running tempest

Addressed by: https://review.openstack.org/607325
    Add new featureset for running tripleo-ui tests

Gerrit topic: https://review.openstack.org/#q,topic:tempest_plugin_venv,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.