[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23027#comment-23027 ] eyal edri [Administrator] commented on OVIRT-858: ------------------------------------------------- [~gshereme@redhat.com] Having these tests under automation dir inside ovirt-engine repo will give you great control and verification on any code that gets into engine, and can potentially block new bad code from getting in, same way any unit tests are running today inside check-patch.sh or check-merge.sh You'll get the full advantage of standard CI (using .packages files for e.g to install any deps you need), you can checkout VDSM tests, they are running it in check-patch and check-merged. You can also limit it to run only on frontend/* files, see examples for it on ovirt-engine check-patch.sh where we check for dal/db files to run dao tests. If your tests are more "heavy" and require not only engine but other projects and you might need to run VMs / hosts as part of it, you should then consider using ovirt-system-tests (and Lago below it). Either way, we can help to add it, just tell us the need/use case and we'll continue from there
new gerrit repo: ovirt-ui-tests -------------------------------
Key: OVIRT-858 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-858 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra
Hi, Please create a new gerrit repo called ovirt-ui-tests. Description: functional tests for oVirt UI, focused around performance testing +2 rights for me, awels, vszocs, oourfali Please mirror it to github. Let me know if you need more information. -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme@redhat.com
-- This message was sent by Atlassian JIRA (v1000.552.6#100018)