Add option to install chrome when running tempest

Change-Id: Ie5892ee14cc5e9bbc09dc79aeac7611bfb26e5bb
Partially-implements: blueprint automated-ui-testing
This commit is contained in:
Honza Pokorny 2018-10-02 14:00:54 -03:00 committed by Chandan Kumar
parent 4c87f1f678
commit 7ff41dea0e
3 changed files with 13 additions and 1 deletions

View File

@ -63,7 +63,8 @@ Role Variables
* `tempest_deployer_input_file`: <file path> The path to tripleo deployer input file which contains the pre configured
configuration for the deployed cloud using TripleO.
* `tempest_os_cloud`: <string> String name of the cloud to export as OS_CLOUD when using clouds.yaml rather than stackrc
* `stackviz_tarball`: <string> Stackviz tarball url to be installed via pip
* `tempest_use_headless_chrome`: true/false - whether the headless chrome docker container should be pulled, and run
* `tempest_headless_chrome_port`: <int> - the entrypoint into the headless chrome container
Skip tests file

View File

@ -99,3 +99,7 @@ tempest_conf_removal_queens:
network-feature-enabled.api_extensions: dvr
tempest_os_cloud: ""
stackviz_tarball: "https://tarballs.openstack.org/package-stackviz-element/stackviz-latest.tar.gz"
# Headless Chrome configuration
tempest_use_headless_chrome: false
tempest_headless_chrome_port: 9999

View File

@ -73,6 +73,13 @@ export CONTAINER_BINARY='docker'
sudo $CONTAINER_BINARY pull {{ tempest_container_registry }}/{{ tempest_container_namespace }}:{{ tempest_container_tag }}
{% if tempest_use_headless_chrome|bool %}
docker pull selenium/standalone-chrome
docker run -d \
-p {{ tempest_headless_chrome_port }}:{{ tempest_headless_chrome_port }} \
-v /dev/shm:/dev/shm selenium/standalone-chrome
{% endif %}
# Run tempest container using docker mouting required files
sudo $CONTAINER_BINARY run --net=host -i -v $TEMPEST_HOST_DATA:{{ tempest_data }} \
-e PYTHONWARNINGS="${PYTHONWARNINGS:-}" \