openQA is a testing framework that allows you to test GUI applications on one hand and bootloader and kernel on the other. In both cases, it is difficult to script tests and verify the output. Output can be a popup window or it can be an error in early boot even before init is executed.
Therefore openQA runs virtual machines and closely monitors their state and runs tests on them.
The testing framework can be divided in two parts. The one that is hosted in this repository contains the web frontend and management logic (test scheduling, management, high-level API, …)
The other part that you need to run openQA is the OS-autoinst test engine that is hosted in a separate repository.
The project’s information is organized into four basic documents. As a first step, read the Starter Guide and then, if needed, proceed to the Installation Guide.
For users of the openQA web interface or the REST API consult Users Guide.
If you are interested in writing tests using openQA read the Tests Developer Guide.
If you are interested in contributing to openQA itself, check the Developer Guide, write your code and send a pull request ;-)
Our main issue tracker is at openQAv3 project in openSUSE’s project management tool. This Redmine instance is used to coordinate the main development effort organizing the existing issues (bugs and desired features) into 'target versions'.
Find contact details and meet developers over our contact page.
openQA is developed on a continuous base where every commit in the git master branch is considered stable and a valid and installable version. The old tags on github are therefore misleading.
All code is licensed under GPL-2-or-later unless stated otherwise
in particular files. This does not apply to code found in the
assets/3rdparty directory. It contains third-party code and the relevant
licenses can be found in the root directory of this code repository.