Skip to content

Test in kanku

Frank Schreiner edited this page Aug 22, 2025 · 5 revisions

Testing open-build-service in kanku

This document gives an overview which scenarios (jobs) are running in our internal kanku instance.

Table of Contents

Kanku job overview

obs-server-($stable|unstable)-*

Stable appliances / Unstable appliances

Current $stable = 2.10

Test our stable/development appliances. We are testing the following images:

  • qcow2
  • install iso
  • raw
  • vdi
  • vmdk

upgrade-*

  • upgrade-26-latest
    • Base installation of OBS-Appliance 2.6
    • Upgrade step by step each major release (2.7/2.8/2.9/2.10)
    • Finally upgrade to obs-server from OBS:Server:Unstable
  • upgrade-29to210
    • Install previous stable OBS-Appliance
    • Upgrade obs-server packages to current stable release
  • upgrade-latest
    • Install current stable OBS-Appliance
    • Upgrade obs-server packages to current unstable packages
  • upgrade-with-storage
    • currently not maintained

wizard-*

wizard install tests are testing the installation of the obs-server packages on a standard dki (devel:kanku:images) image. dki images are minimalistic images of the major distributions (similar to openSUSE's JeOS images) with some minor modifications to make them more suitable for kanku. Our test cases only cover the current SLE/openSUSE releases.

General Appliance Tests

  • include.d/obs-server-common/test-appliance.yml
    • Check if obsapisetup service is active
    • Check if signer certs are created successfully
  • include.d/obs-server-common/test-registry.yml
    • Check if local OBS provides a docker registry compatible API
    • Check if upload gets blocked correctly (may be legacy test which could be removed nowadays)
  • include.d/obs-server-common/test-frontend.yml
  • include.d/obs-server-common/test-building.yml
    • tests located under https://github.com/openSUSE/open-build-service/tree/master/dist/t/osc
    • test api using osc
      • configure interconnect
      • create home project for user Admin
      • create subproject of home:Admin using scmbridge
      • create legacy package in obs and check build results
      • create git workflow package in gitea/obs and check build results
      • test container building
        • branch container "package" from openSUSE.org via interconnect
        • check "package" build result
        • check container registry of local OBS instance
  • include.d/obs-server-common/test-reboot.yml
    • just testing if appliances are reboot save

Special test cases

Kanku::Handler::OBSServerFrontendTests Code

  • executed on a configurable jump host
  • simulates real user interaction
  • does not modify the target system
  • saves logs/screenshot in jump host's webroot
Clone this wiki locally