forked from pool/openQA
Better description in openQA.spec
OBS-URL: https://build.opensuse.org/package/show/devel:openQA:tested/openQA?expand=0&rev=9
This commit is contained in:
parent
c3f54bcbec
commit
adf53689cd
21
openQA.spec
21
openQA.spec
@ -99,10 +99,23 @@ BuildArch: noarch
|
||||
%requires_eq perl-Mojolicious-Plugin-AssetPack
|
||||
|
||||
%description
|
||||
The openQA framework consists of two parts, which are tracked in
|
||||
separate git repos. The OS-autoinst test engine and the front-end
|
||||
with web-interface, test-scheduler and other high-level logic, which
|
||||
is part of this repo.
|
||||
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.
|
||||
|
||||
openQA is an automated test tool that makes it possible to test the whole
|
||||
installation process of an operating system. It uses virtual machines to
|
||||
reproduce the process, check the output (both serial console and screen) in
|
||||
every step and send the necessary keystrokes and commands to proceed to the
|
||||
next. openQA can check whether the system can be installed, whether it works
|
||||
properly in 'live' mode, whether applications work or whether the system
|
||||
responds as expected to different installation options and commands.
|
||||
|
||||
Even more importantly, openQA can run several combinations of tests for every
|
||||
revision of the operating system, reporting the errors detected for each
|
||||
combination of hardware configuration, installation options and variant of the
|
||||
operating system.
|
||||
|
||||
%package common
|
||||
Summary: The openQA common tools for web-frontend and workers
|
||||
|
Loading…
Reference in New Issue
Block a user