openQA web-frontend, scheduler and tools.
Perl JavaScript Perl 6 CSS Shell PLpgSQL Other
Clone or download
foursixnine Merge pull request #1724 from Martchus/fix_incomplete_frame
Improve code for devel mode, fix 'Data frame received after close'
Latest commit eff15ef Jul 20, 2018
Failed to load latest commit information.
assets devel mode: Prevent endless, instant reconnects on error Jul 18, 2018
dbicdh Add blocked_by to jobs - calculated on job changes Jul 9, 2018
docker Use docker image from OBS (#1685) Jun 18, 2018
docs Update Jul 16, 2018
etc Mention how to actually enable openqa-ssl.conf under openSUSE Jul 17, 2018
lib Merge pull request #1724 from Martchus/fix_incomplete_frame Jul 20, 2018
profiles/apparmor.d Update apparmor profile for worker (#1645) May 4, 2018
public Remove symlinks for Glyphicon fonts Apr 13, 2018
script Merge pull request #1713 from Martchus/refactor_docker_test_script Jul 9, 2018
systemd Update service file for livehandler service Jun 26, 2018
t Merge pull request #1724 from Martchus/fix_incomplete_frame Jul 20, 2018
templates Don't display blocked jobs as scheduled Jul 9, 2018
.gitignore Ignore profiling data generated by nytprof May 15, 2018
.openqa-travis.enc Update key to official one in os-autoinst/openQA Jan 2, 2017
.perlcriticrc Fix perlcritic errors Mar 18, 2017
.perltidyrc Add a 120 column limit to .perltidyrc (#1017) Nov 17, 2016
.travis.yml Use docker image from OBS (#1685) Jun 18, 2018
.vimrc fix vimrc to actually only trigger where it should Apr 4, 2014
COPYING install actual COPYING file Feb 25, 2014
Makefile Remove docker-tests during install Jul 9, 2018
README.asciidoc Add a Contributing section Apr 7, 2017
codecov.yml Increase the required coverage to 88.8 May 2, 2018
cpanfile Require 'Selenium::Remote::WDKeys' in CPAN file Apr 25, 2018
openQA-test.spec Use docker image from OBS (#1685) Jun 18, 2018
openQA.spec Use docker image from OBS (#1685) Jun 18, 2018



badge openQA

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.

Getting started

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 ;-)

Issue trackers and support

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'.

Currently developers meet in IRC channel #opensuse-factory