[ 
https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Sheremeta updated OST-99:
------------------------------
    Description: 
I'm writing a suite that does headless UI testing. One goal is to open headless 
firefox and actually open the UI, perform a login, make sure things look good, 
make sure there are no ui.log errors, etc. I'll also eventually add chromium, 
which can run headless now too.

The suite requires several firefox versions to be installed on the test 
machine, along with chromium. There are also some binary components required, 
geckodriver and chromedriver. These are not packaged.

Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, 
/opt/chromium62, etc. on the machine running the suite. So I think it makes 
sense to maintain a custom rpm with all of this.

Where can this rpm live? What is a reliable way to do this? (I know we want to 
avoid copr.)

...

Update for posterity (Mar 11 2018): we decided in the comments below to use 
[Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and 
[docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Docker-Compose].
 Since Selenium Grid provides preconfigured containers, we're not maintaining 
anything other than docker-compose yaml files. No need to worry about packaging 
browsers ourselves.

---

https://gerrit.ovirt.org/#/c/67166

  was:
I'm writing a suite that does headless UI testing. One goal is to open headless 
firefox and actually open the UI, perform a login, make sure things look good, 
make sure there are no ui.log errors, etc. I'll also eventually add chromium, 
which can run headless now too.

The suite requires several firefox versions to be installed on the test 
machine, along with chromium. There are also some binary components required, 
geckodriver and chromedriver. These are not packaged.

Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, 
/opt/chromium62, etc. on the machine running the suite. So I think it makes 
sense to maintain a custom rpm with all of this.

Where can this rpm live? What is a reliable way to do this? (I know we want to 
avoid copr.)

...

Update for posterity (Mar 11 2018): we decided in the comments below to use 
[Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and 
[docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Docker-Compose].
 Since Selenium Grid provides preconfigured containers, we're not maintaining 
anything other than docker-compose yaml files. No need to worry about packaging 
browsers ourselves.


> new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
> ------------------------------------------------------------------------------
>
>                 Key: OST-99
>                 URL: https://ovirt-jira.atlassian.net/browse/OST-99
>             Project: oVirt system tests
>          Issue Type: Improvement
>            Reporter: Greg Sheremeta
>            Assignee: infra
>
    



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Reply via email to