QA (public) » openQA Project (public) » openQA Tests (public)

Some proposals:

• Creating a project os-autoinst-utils-opensuse that contains all the common functionality (for example, everything within /lib)
• Creating a project os-autoinst-utils-gnulinux that contains all the common functionality, but in a more general way so it can be reused by any GNU/Linux distribution
• Having those modules as git sub modules of os-autoinst-distri-opensuse.

Bad idea from my POV. This will means 3 PRs (tests/needles/lib).

With this reasoning we can also separate /data subfolder when someone need only those files.
Would make it easier for single person and harder for everybody else.

Why is openqa-in-openqa separate git project, not just separate test scenario (in os-autoinst-distri-opensuse)?

mkravec wrote:

Why is openqa-in-openqa separate git project, not just separate test scenario (in os-autoinst-distri-opensuse)?

Well, one reason is so that it exactly motivates this ticket, actually :) There are more test distributions which we are hardly or not aware of, e.g. https://pagure.io/fedora-qa/os-autoinst-distri-fedora , and it would be great if we can share more with them as well. So merging os-autoinst-distri-openQA into os-autoinst-distri-opensuse is one option but it will not solve the overall, more general change.

Just vendor (copy and paste) the libs you want. In a project this size and complexity you generally want to avoid creating dependencies because it is more work to maintain them and play nice with others than to reimplement the specific features we need.

If you want to be nice to third parties, then sure, fork our test code and turn it into a lib or a linux distri template. If third parties add useful stuff to it then we can cherry pick it back into our distri.