Hi all, since we as the Yast team decided to increase our test coverage, we were creating and submitting several tests to openQA in the past and we would like to continue doing that. In some cases it felt quite complicated to get those tests merged and running in the official instances. To make contribution of tests easier and more straightforward I think it would be helpful to define some rules and methods about - how to handle differences between openSUSE and SLE in regards of testing. - how to keep the balance between test coverage and testing speed means: which tests should go into which test suites or maybe even a better definition of what all the test suites are actually supposed to be good for. - define a coding style in regards of how things should be done, e.g defining/checking for ENVs vs. check_screen, when to soft fail vs. die() etc. Clearly defined rules make it easier to avoid discussions in PRs since people involved might currently have different opinions how a proper test should look like. So I suggest to set up a meeting to discuss and write down a first version of an openQA contribution manifest. I think the right people wo that should be from QA (rbrown?), openSUSE (coolo?), SLEPOS (nadvornik?) and YaST (myself) - anyone else interested? Mit freundlichen Grüßen, Christopher Hofmann -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org