[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

3 Apr 2018

      This is a multi-part message in MIME format...

------------=_1522780386-19863-450
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

     [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugi... ]

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-Dock...]. 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.

---

Update for posterity (Apr 3 2018):
docker-compose doesn't work, but using a network and passing the hub IP (not container name) to the nodes does.

---

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-Dock...]. 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
...
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)

------------=_1522780386-19863-450
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugi... ]</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>Update for posterity (Apr 3 2018): docker-compose doesn't work, but using a network and passing the hub IP (not container name) to the nodes does.</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>
<p>---</p>
<p><a href="https://gerrit.ovirt.org/#/c/67166">https://gerrit.ovirt.org/#/c/67166</a></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-2BJ33BSM3t..." 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>

------------=_1522780386-19863-450--

Greg Sheremeta (oVirt JIRA)

tags

participants (1)