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

2 Mar 2018


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

------------=_1519999376-14302-262
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35928#comment-35928 ] 

Greg Sheremeta commented on OST-99:
-----------------------------------
...
I would not start with the container
I'm close to having something pretty nice with docker-compose and the docker API via OST :)
...
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
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.)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100081)

------------=_1519999376-14302-262
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 commented on OST-99:</h3>
<blockquote><p>I would not start with the container</p></blockquote>
<p>I'm close to having something pretty nice with docker-compose and the docker API via OST :)</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>
<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. 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.)</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</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>

------------=_1519999376-14302-262--

Greg Sheremeta (oVirt JIRA)

tags

participants (1)