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

Barak Korren commented on OVIRT-1788:
-------------------------------------

[[email protected]] I can make the 1st one for you, making a CentOS 
container with firefox installed in it is easy enough, the real challenge for 
me would be how to make it run headless and talk to the testing framework and 
oVirt.

What testing framework do you intend to use? How does it communicate with the 
browsers it uses for testing? Does it has built-in support to the situation 
where the browsers are running on different containers or hosts then the 
testing framework (Processes in different containers typically look to one 
another as if they are on different hosts)?

> 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)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra

Reply via email to