[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
eyal edri moved OVIRT-1788 to OST-99: ------------------------------------- Component/s: (was: OST) Project: oVirt system tests (was: oVirt - virtualization made easy) Workflow: Software Simplified Workflow for Project OST (was: Task Management Workflow) Key: OST-99 (was: OVIRT-1788) > 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#100077)
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra