[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
Barak Korren (oVirt JIRA)
jira at ovirt-jira.atlassian.net
Tue Dec 5 16:49:44 UTC 2017
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35459#comment-35459 ]
Barak Korren commented on OVIRT-1788:
-------------------------------------
Well, can the command it uses to launch firefox be customized?
We need to somehow figure out how it talks to firefox once it launches it.
Can you elaborate a bit about that '(roughly)' part?
How did you intend to make it work with different browser versions if they were installed in '{{/opt}}' ?
> new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
> ------------------------------------------------------------------------------
>
> Key: OVIRT-1788
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST
> 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#100074)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20171205/b6eb2ad1/attachment.html>
More information about the Infra
mailing list