Skip to content

b10n1k/openQA

This branch is 1 commit ahead of, 181 commits behind os-autoinst/openQA:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

878d06e · Jan 28, 2025
Oct 10, 2024
Aug 5, 2024
Dec 17, 2024
May 13, 2024
Dec 2, 2024
Dec 19, 2024
Oct 9, 2024
May 23, 2023
Jan 22, 2025
Jan 10, 2025
Jan 14, 2025
Sep 17, 2024
Jan 28, 2025
Jan 24, 2025
Apr 19, 2024
Jan 10, 2025
Jan 14, 2025
Jan 24, 2025
Jan 16, 2025
Jan 25, 2025
Aug 25, 2021
Jul 29, 2021
Jan 17, 2019
Feb 12, 2024
Aug 23, 2024
Aug 13, 2024
Jan 15, 2025
Jul 13, 2021
Aug 8, 2024
Apr 4, 2014
Jan 23, 2024
Jan 23, 2024
Feb 25, 2014
Feb 12, 2024
Jan 20, 2025
Jun 4, 2024
Oct 16, 2024
Jan 22, 2025
Jan 22, 2025
Apr 8, 2024
Jan 20, 2025
Jan 20, 2025

Repository files navigation

openQA

badge CircleCI badge?arch=x86 64&distri=openqa&flavor=dev&machine=64bit 2G&test=openqa install%2Bpublish&version=Tumbleweed

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.

Try out running tests with openQA in a browser in our Codespace. See also: GitHub Codespaces documentation

See openQA in a browser for documentation on how to use it.

Contributing

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

Find contact details and meet developers over our contact page.

Releases

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.

License

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.

About

openQA web-frontend, scheduler and tools.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Perl 86.5%
  • JavaScript 8.2%
  • Shell 1.8%
  • SCSS 1.4%
  • PLpgSQL 0.6%
  • Makefile 0.4%
  • Other 1.1%