Ubuntu
openqa package

openqa 4.6.1700240294.34068e38e-2 source package in Ubuntu

Changelog

openqa (4.6.1700240294.34068e38e-2) unstable; urgency=medium

  * Build-Depends on systemd-dev (closes: 1060501)
  * limit build-deps for testing to <!nocheck>
  * avoid deprecation warnings regarding `spurt`

 -- Philip Hands <email address hidden>  Thu, 11 Apr 2024 08:33:02 +0200

Upload details

Uploaded by:
Philip Hands
Uploaded to:
Sid
Original maintainer:
Philip Hands
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Noble release universe misc

Builds

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
openqa_4.6.1700240294.34068e38e-2.dsc 5.0 KiB 52f2826fa95dc8e6d0d08a6855ae329567cc5550168eb9d42eeae4a8047cdd51
openqa_4.6.1700240294.34068e38e.orig.tar.xz 1.9 MiB fa5c169e9f78ace572f5075e2dc97c9e3aa2029be2695ec52663e52dbdd2971f
openqa_4.6.1700240294.34068e38e-2.debian.tar.xz 1.2 MiB b7943b8bce030cfc6f65c833445cd96c481cbf6646d464301c83f3435d138c39

No changes file available.

Binary packages built by this source

openqa: automatic Operating System testing framework (webUI & scheduler)

 openQA is a testing framework that allows you to run tests on pretty-much
 anything that you can get 'remote' control of (most often, anything you can run
 in a VM and point VNC at). This allows testing of things including GUI
 applications, system boot-up (BIOS, bootloaders, kernels), installers and whole
 operating systems.
 .
 Tests (using Perl syntax) generally consist mostly of sequences of code like:
   assert_and_click 'some_icon';
   assert_screen 'some_prompt';
   send_key 'ret';
 which are run using the os-autoinst test engine, by a worker. The tags named in
 scripts can then be associated with 'needles' (elements of screenshots) via the
 webUI (either from past tests, or while controlling a live test). Other testing
 possibilities include: serial-connected headless systems, multi-host networked
 tests, and non-VM 'real' systems.
 .
 This package includes the job scheduler, the elements providing the services to
 allow workers to run tests and upload results, and the Web-based user
 interface.

openqa-client: automatic Operating System testing framework (utilities)

 This package includes scripts such as 'openqa-cli' and 'openqa-clone-job' to
 provide easy control of openQA servers, via the REST API, as well as commands
 useful when administering an OpenQA server.
 .
 openQA is a testing framework that allows you to run tests on pretty-much
 anything that you can 'remotely' control. For instance, a VM that can be
 accessed via VNC.

openqa-common: automatic Operating System testing framework (common files)

 This package contains shared resources for openQA web front-end and openQA
 workers.
 .
 openQA is a testing framework that allows you to run tests on pretty-much
 anything that you can 'remotely' control. For instance, a VM that can be
 accessed via VNC.

openqa-doc: automatic Operating System testing framework - documentation

 Documentation for openQA (and the associated os-autoinst test engine), covering
 topics including: installation, configuration, and basic test writing.
 .
 openQA is a testing framework that allows you to run tests on pretty-much
 anything that you can 'remotely' control. For instance, a VM that can be
 accessed via VNC.

openqa-worker: automatic Operating System testing framework (worker)

 openQA is a testing framework that allows you to run tests on pretty-much
 anything that you can get 'remote' control of (most often, anything you can run
 in a VM and point VNC at). This allows testing of things including GUI
 applications, system boot-up (BIOS, bootloaders, kernels), installers and whole
 operating systems.
 .
 Tests (using Perl syntax) generally consist of little more than sequences like:
 assert_and_click 'some_icon'; assert_screen 'some_prompt'; send_key 'ret';
 which are run using the os-autoinst test engine, by a worker. The tags named in
 scripts can then be associated with 'needles' (elements of screenshots) via the
 webUI (either from past tests, or while controlling a live test). Other testing
 possibilities include: serial-connected headless systems, multi-host networked
 tests, and non-VM 'real' systems.
 .
 This package is to be installed on a worker system (which may also be acting as
 a server). Workers register with a server (or perhaps multiple servers), and
 can then accept jobs, and run tests (using the os-autoinst test engine).