<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre>
<h3>Greg Sheremeta updated OST-99:</h3>
<pre>Description:</pre>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p>
<p>…</p>
<p>Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|<a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a>] and [docker-compose|<a href="https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Docker-Compose">https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Docker-Compose</a>]. 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.</p>
<p>---</p>
<p><a href="https://gerrit.ovirt.org/#/c/67166">https://gerrit.ovirt.org/#/c/67166</a></p>
<pre>was:</pre>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p>
<p>…</p>
<p>Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|<a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a>] and [docker-compose|<a href="https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Docker-Compose">https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-Docker-Compose</a>]. 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.</p>
<blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3>
<pre> Key: OST-99
URL: https://ovirt-jira.atlassian.net/browse/OST-99
Project: oVirt system tests
Issue Type: Improvement
Reporter: Greg Sheremeta
Assignee: infra</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3tuiUfRTk64K-2BOjH-2Brod5IlW2oCW2L6mmZR4CqZP8-2Fo2mgksV-2FYoRa1KKSyaHxiHy7u3Ic70psYh3BcrXZiTitLSss6vjRIvZwRnqzcsUnXl2fYBC8D1FsJhhv3USWqic26zvbCvDpaDvm9ZfemGyKMMj-2BDJGgZiQz8vAtILAMzDYXLjHVtommuM2vR0HI3tBpOte0Q3io05wdjHX7kdD59QCxDKDXAqdD2Z9TInXn-2BNFk2F-2F0IfqIyKfTY5fosTuHgBqIKoATC1WLgO-2FTq0t8xQqACZvY7wruQCruf-2FRQbE7A7a1S8mhntnXGnwHquo2IQcD-2Fsvvs0YO8NDaPxj6-2FLd0gIxGIwqteVGtjoPgzdQ7ZiCFjnUDZIG9MUZdVgf5mh1nOE31DulXm-2BZMzZ6YWj-2F1fGju-2B2Yg34mv" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>