Jlaska/Draft

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

This page is intended to outline the current state of automated installer tests, identify possible short-term objects and identify task owners.

Existing Installer Tests

This section lists tests or scripts that are used now during manual verification of the installer.

checkbot.sh - runs multiple tests
1. Build test - runs ./autogen.sh && ./configure.sh && make
2. Pylint test - Runs tests/pylint/runpylint.sh
tests/anaconda_storage - Storage unit testsuite in the clumens branch of autoqa.git
compose-tree script - Script that creates a mock chroot and creates install images using pungi (see also instructions)
tests/rats_install/install.py - AutoQA test script that does a basic automated kickstart install

Scope: The patchset in the clumens autoqa branch may need to be refreshed to master and re-run to check for proper operation. This idea involves rebasing the patch to master, and re-running the tests to ensure they continue to work.
Skill Level: Advanced
Owner: unassigned

Scope: Currently, anaconda-devel uses a script called checkbot.sh to run pylint and make against anaconda source. This script would be pulled into AutoQA as a new test. Eventually, the test would be run after git commits, but in the short-term, could run on a nightly basis.
Skill Level: Moderate
Owner: unassigned

Scope: To support triggering tests based on git commits, create a new AutoQA watcher.
Skill Level: Moderate
Owner: unassigned

Scope: Create a new AutoQA test using the compose-tree script that runs pungi inside a mock chroot. This test is intended to run after a koji build of anaconda or it's dependent packages.
Skill Level: Moderate
Owner: unassigned