Needle updates to sync with prod
openQA tests for the Rocky Linux distribution
This repository contains tests and images for testing Rocky with openQA. The fedora_openqa library and CLI are used for scheduling tests, and createhdds is used for creating base disk images for the test. For openQA installation instructions, see the Fedora openQA wiki page.
Issues and pull requests are tracked in os-autoinst-distri-fedora Pagure. Pagure uses a Github-like pull request workflow, so if you're familiar with that, you can easily submit Pagure pull requests. If not, you can read up in the Pagure documentation.
Obviously, this repository is little use without access to an openQA installation. Also, the tests themselves require the perl libraries JSON and REST::Client to be installed on the worker host; in Fedora, the package names are
perl-REST-Client. To load templates from this repository, you will need the upstream client tools (packaged as
openqa-client in Fedora) and the dependencies of
fifloader.py (see below for more on this tool) installed. Those dependencies are Python 3 and the
jsonschema library. For running the unit tests, you will additionally need
See official documentation on:
- basic concept
- test development (including API specification)
- needles specification
- supported variables for backend.
See this example repo on how tests should be structured.
See the results readme for the expected test commands and results for Rocky
FIF template format
The test templates in this repository (files ending in
fif.json) are not in the same format as expected by and are not directly compatible with the upstream template loader. They are in a format referred to as 'FIF' ('Fedora Intermediate Format') which is parsed into the upstream format by the
fifloader.py utility found in this repository. This format is intended to be more convenient for human reading and editing. It is more fully explained in the docstring at the top of
fifloader.py. Please refer to this when adding new tests to the templates. A command like
./fifloader.py --load templates.fif.json templates-updates.fif.json can be used to load templates in the FIF format (this converts them to the upstream format, and calls the upstream template loader on the converted data). See
./fifloader.py -h for further details on
main.pm modular architecture
Since openQA uses only one entrypoint for all tests (main.pm), we have decided to utilize this feature and make tests modular. It means that basic passing through main.pm (without any variables set) results in most basic installation test executed. Developer can customize it with additional variables (for example by setting
PACKAGE_SET=minimal to do installation only with minimal package set).
Make your test modular, so that it utilizes
_do_install_and_reboot.pm tests (that are loaded automatically). Break your test into smaller parts, each dealing with one specific feature (e. g. partitioning, user creation...) and add their loading into main.pm based on reasonable variable setting (so they can be used in other tests also).
Fedora installation (and consequently main.pm) consists of several parts:
Booting into Anaconda or booting live image and starting Anaconda
Since there isn't much variation between tests in this step, we have developed universal
_boot_to_anaconda.pm test that is loaded automatically each time except when
UPGRADE is set (see VARIABLES.md).
To customize this step, you can set following variables:
GRUBis appended to kernel line before boot. You can set for example
KICKSTARTis set, this part of installation ends here (program doesn't wait for Anaconda to appear). Note that you should set
inst.ksyourself by setting
LIVEis set, program waits for desktop to appear and then clicks on "Install to Hard Drive" button.
Customizing installation by interacting with Anaconda spokes
Most of the differences between tests take place in this part. If you want to add another installation test, you will probably put your variable checking and test loading here. All tests in this part should start on Anaconda's main hub and after they done its part, they should go back to Anaconda's main hub so that next test could be executed. In this phase, universal
_software_selection.pm test is loaded that handles selecting what software to install.
To customize this step, you can set following variables:
PACKAGE_SETto install required package set on "Software selection spoke" - you have to provide correct needles with the name of
ENCRYPT_PASSWORDto encrypt disk, value of this variable is used as an actual password.
Installing Rocky Linux and waiting for Rocky Linux to reboot
After all customizations are finished,
_do_install_and_reboot.pm test is automatically loaded. It starts installation, creates user and sets root password when required, waits for installation to finish and reboots into installed system. Only variables that control flow in this part are these:
ROOT_PASSWORDto set root password to this value.
- When set,
USER_PASSWORDare used to create user in Anaconda.
After installation is finished and installed system is fully booted, you can run additional tests as checks that installed system has correct attributes - that correct file system is used, that RAID is used etc.
Your test can inherit from
anacondatest. Each provides relevant methods that are documented in-line, so read the files (
lib/installedtest.pm) for information on these.
basetest: A base class provided by os-autoinst - it has empty
post_fail_hook()and doesn't set any flags.
anacondatest: should be used in tests where Anaconda is running. It uploads Anaconda logs (for example
installedtest: should be used in tests that are running on installed system (either in postinstall phase or in upgrade tests).
There are also several modules that export utility functions, currently
tapnet. Your test can
use any of these modules and then directly call the functions they export. Again, the functions are documented in-line.
New test development workflow
- Put each part of your test as a separate file into
test_flags()method, inheriting from one of the classes mentioned above.
- Set correct variables (so that all test parts you have made are executed) in WebUI -> Test suites.
- Link your newly created Test suite to medium type in WebUI -> Job groups.
- Run test (see fedora_openqa repository).
- Create needles (images) by using interactive mode and needles editor in WebUI.
- Add new test suite and profiles into
templates-updates.fif.json, if the test is applicable to the update testing workflow)
- Add new Test suite and Test case into
conf_test_suites.pyfile in fedora_openqa repository.
tox. This will check the templates are valid.
- Open pull request for the os-autoinst-distri-fedora changes in Pagure. Pagure uses a Github-style workflow (summary: fork the project via the web interface, push your changes to a branch on your fork, then use the web interface to submit a pull request). See the Pagure documentation for more details.
- Open a pull request in fedora_openqa Pagure for any necessary fedora_openqa changes.
Tests can run in different languages. To set the language which will be used for a test, set the
LANGUAGE variable for the test suite. The results of this will be:
- The value set will be typed into the language search box in anaconda.
- Any needle with at least one tag that starts with
LANGUAGEwill be unregistered unless it has the tag
(LANGUAGE)is the value set, forced to upper-case).
- As a consequence, the chosen language will be selected at the anaconda Welcome screen.
It is very important, therefore, that needles have the correct tags. Any needle which is expected to match for tests run in any language must have no
LANGUAGE tags. Other needles must have the appropriate tag(s) for the languages they are expected to match. The safest option if you are unsure is to set no
LANGUAGE tag(s). The only danger of this is that missing translations may not be caught.
Note that tags of the form
ENV-INSTLANG-(anything) are useless artefacts and should be removed.
Contribution Approval Guidelines
Use the following guidelines to understand the level of approval needed to merge your contributions:
- Pull requests and merge requests to a non-default branch will require 1 visual inspection approval to merge, provided all comments are addressed and no requests for followup are outstanding.
- Pull and merge requests to the default branch (
rocky) require 2 visual inspection approvals and 1 openQA automation approval to merge.
- When public openQA infrastructure is available, all pull requests should initiate an openQA build, which must pass prior to merge.
Licensing and credits
The contents of this repository are available under the GPL, version 3 or any later version. A copy is included as COPYING. Note that we do not include the full GPL header in every single test file as they are quite short and this would waste a lot of space.
The tools and tests in this repository are maintained by the Rocky Linux QA team. We are grateful to the openSUSE team for developing openQA, to the Fedora QA team for their respin and for the openSUSE tests and Fedora tests on which this repository was initially based (and from which occasional pieces are still borrowed).