[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
Yaniv Kaul (oVirt JIRA)
jira at ovirt-jira.atlassian.net
Thu Mar 1 15:07:03 UTC 2018
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35926#comment-35926 ]
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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20180301/47e6c035/attachment-0001.html>
More information about the Infra
mailing list