openQA has a well earned reputation as a 'full system' testing tool, able to test a system end-to-end from the operating system to it's applications on a number of different platforms and architectures, including VM's & Bare Metal.

But one area of weakness is it's usefulness as a testing tool for developers or packagers. openQA can easily test a package once it's INSIDE a distribution, but how do you test that package BEFORE submitting it to the distribution?

openSUSE/SLE has the concept of 'staging', where we utilise OBS and openQA to basically create 'what-if' builds's for the whole OS where we can do basic validation tests to ensure a proposed check-in doesn't break the OS or it's basic functionality, but staging doesn't test the package itself

This hackweek project will experiment with solutions to this problem.

Concepts to be investigated include

  • Providing reference disk images for package-specific tests for each OS (SLE, Tumbleweed, Leap)
  • Injecting test code into openQA without needing it to be submitted via github. This might include openQA tests being stored as part of the OBS package.
  • Loading package-specific tests in openQA by feeding openQA variables over its REST API
  • Booting these reference images to either a console or X11 as required by the test
  • Testing and providing the results in a meaningful way to the Developer

I will try to find solutions to the above which will work in the following contexts

  • a Developer working 'packageless' with just a git repo and a local compiler (unlikely, but still want to think about it)
  • a Developer working on a package in their OBS Home/Devel project
  • Release Management/Devel Project reviewers of an OBS submit request wanting to see the results of Package Testing BEFORE deciding whether or not the package can be checked-in or forwarded to staging

Looking for mad skills in:

perl openqa obs

This project is part of:

Hack Week 15


  • over 1 year ago: tbechtold liked openQA Package Testing
  • over 1 year ago: pgeorgiadis liked openQA Package Testing
  • over 1 year ago: szarate liked openQA Package Testing
  • over 1 year ago: bchou liked openQA Package Testing
  • over 1 year ago: okurz liked openQA Package Testing
  • Show History


    • RBrownSUSE
      over 1 year ago by RBrownSUSE | Reply

      Part 2 - Autogenerate X11 tests from Desktop files in packages - including booting the image for the first time, running the app for the first time, and autoneedling for the first time

    • tbechtold
      over 1 year ago by tbechtold | Reply

      Maybe interessting is the system Debian/Ubuntu uses called autopkgtest. See also

      • pgeorgiadis
        over 1 year ago by pgeorgiadis | Reply

        I watched the relevant talk at FOSDEM and it seems really great the fact that they are running all the upstream testsuites plus the fact that they trigger these testsuites against the package's reverse dependencies... (!) But autopkgtest it's tighten only to Debian, which means we can't just take it and use it as it is. We have to come up with our own equivalent system. But the most important part here is that the developers/maintainer has to take care about these upstream tests, so IMHO there has to be an agreement that the src rpm should include the tests into them, and build service has to have the resources + the knowledge on how to run them; then either reject or forward the update up to openQA.

    Similar Projects

    openQA IDE by coolo

    There is a running gag built into openQA called...

    Make YaST Testing Independent of Keyboard Shortcuts by shundhammer

    Motivation / Problem

    Right now, our QA tea...

    Setup UEFI HTTPBoot with OVMF and try to write/run test on openQA by bchou

    HTTPBoot was added into UEFI SPEC since 2.5. It...

    MirrorPinky by darix

    *A web frontend for the mirrors in the mirrorbr...

    Kubic Desktop - aka Sgt Peppers Read Only Hearts Club Band by RBrownSUSE

    The Kubic Project currently produces a "CaaSP-l...