Ubuntu
openqa package

openqa 4.6.1732034221.ae34b08ff-2 source package in Ubuntu

Changelog

openqa (4.6.1732034221.ae34b08ff-2) unstable; urgency=medium

  [ Roland Clobus ]
  * use Debian changelog to discover a version to show (closes: 1077069)

  [ Philip Hands ]
  * Remove cropper.css (it is unused)
  * avoid running tidy tests during build

 -- Philip Hands <email address hidden>  Tue, 08 Apr 2025 09:30: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
Questing release universe misc

Builds

Questing: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
openqa_4.6.1732034221.ae34b08ff-2.dsc 5.1 KiB 631344ce0dd075f3c1ec678b4baa1b5c2204deb779d9332fe44e25be545ce1f5
openqa_4.6.1732034221.ae34b08ff.orig.tar.xz 2.0 MiB 878108e98120ba0d241f60b2c02394b139c65cddfb2c4cc12aea0486bfb8cda8
openqa_4.6.1732034221.ae34b08ff-2.debian.tar.xz 27.4 KiB ceb00c8fb1e6318ec8e9527342d253544a8ffe66f448c82b4e0beeb41735ed15

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