[JIRA] (OVIRT-858) new gerrit repo: ovirt-ui-tests

[ https://ovirt-jira.atlassian.net/browse/OVIRT-858?page=com.atlassian.jira... ] Barak Korren commented on OVIRT-858: ------------------------------------ {quote} This is meant to test only the UI. It's used in conjunction with vdsmfake (typically) so that only the UI / engine are under perf test. However, it could be used down the line to do full stack tests – it's webdriver {quote} Well, tests that get put inside a project repo are typically meant to be run per-patch (via check_patch.sh) or pre-merge (via check_merged.sh once we get merge-gating to work). If those are meant to run in one of these scenarios, then by all means, put them in the engine repo. If the tests are not meant to be used are part of the decision-making process for merging a patch to a particular project, then they go in ovirt-system-tests. {quote} I've looked into ovirt-system-tests in the past, but I'm afraid I don't have time right now to look deeply and figure out where to put this. Can you make a guess and let me know which directory I can use? Perhaps a new one? {quote} Well, infrastructure-style files (like the web driver itself) that will be shared by multipile tests can probably go in a new directory, probably under 'common'. With regard to particular tests, that depends on what is the purpose and output of the tests: If those tests should be counted towards the conclusion that "oVirt is stable" then they should probably be collected in numbered files under the `basic-suit-*/test-scenarios` directories. If the tests are for generating various metrics and collecting data (And have no yes/no conclusions) the those should probably be collected in a new test suit. -- This message was sent by Atlassian JIRA (v1000.552.6#100018)