QA » openQA Project

User Story¶

As a developer of any software on github I want to execute an openQA test on a production server based on a pull request of my software to not need a local openQA instance without needing to extend openSUSE "osado" tests. I just need a booted Tumbleweed to start my software on :)

Further details¶

okurz:
Had a nice discussion with trenn: https://github.com/cobbler/cobbler/pull/2024 is a nice example of what one would desire to do in openQA instead, e.g.

1. pull request in github triggers openQA test
2. openQA test executes a custom test defined in the github source repo of the product under test (cobbler in this case)
3. openQA test only boots a VM image, e.g. Tumbleweed, and executes the custom module
4. test result is fed back to the github PR

implementation suggestions:

1. using latest os-autoinst-distri-opensuse plus – as custom assets currently do not work – a custom test module that same what we tried already for HPC gets the defined test script, could be anything downloadable and executable, and runs it
2. use SCHEDULE parameter with e.g. SCHEDULE=tests/boot/boot_to_desktop,tests/run_custom
3. github API access relying on test variables previously provided on trigger
4. Allow to compute the HDD image path dynamically, e.g. by providing a regex which is matched against existing assets on the openQA instance. This would allow utilizing an existing image in a dynamic way (e.g. to use the image created by the installation job for the most latest Tumbleweed snapshot as the openQA-in-openQA test does).
5. Add mechanism to avoid users from spamming jobs.