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

Thursday, 1 March 2018

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

------------=_1519916823-27449-246
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

Yaniv Kaul commented on OST-99:
-------------------------------

I think it'd be easier to start with running those tests from the Engine VM, though I
really like the containers idea - if it works well, we can probably use container for
other areas as well (storage !).

I would not start with the container just because it'll offset us from our main goal
of getting the UI automation in.

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

------------=_1519916823-27449-246
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.pl...
]</pre>
<h3>Yaniv Kaul commented on OST-99:</h3>
<p>I think it'd be easier to start with running those tests from the Engine VM,
though I really like the containers idea &ndash; if it works well, we can probably use
container for other areas as well (storage !).</p>
<p>I would not start with the container just because it'll offset us from our
main goal of getting the UI automation in.</p>
<blockquote><h3>new ui_sanity scenario for basic_suite &mdash; 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>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100081)</p>

------------=_1519916823-27449-246--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011