User:Jlaska/Draft: Difference between revisions

Revision as of 20:34, 12 November 2010

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

Project Ideas

Update AutoQA storage unit testsuite

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

Integrate checkbot.sh with AutoQA

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

Create post-git-commit AutoQA hook

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

Automate Installation test matrix

Scope: Automate installation test matrix (see Is_anaconda_broken_proposal)
Skill Level: Advanced
Owner: unassigned

New post-koji-build test to run pungi

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

@@ Line 3: / Line 3: @@
 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 =
+== Existing Installer Tests ==
+This section lists tests or scripts that are used now during manual verification of the installer.
 # {{filename|checkbot.sh}} - runs multiple tests
 ## Build test - runs {{command|./autogen.sh && ./configure.sh && make}}
 ## Pylint test - Runs {{command|tests/pylint/runpylint.sh}}
 # {{filename|tests/anaconda_storage}} - Storage unit testsuite in the <code>clumens</code> branch of [http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=tests/anaconda_storage;h=0d06525d8bf0be410b5c67e15cf815a53e8b7f9f;hb=refs/heads/clumens autoqa.git]
-# {{filename|scripts/buildinstall}} - Used by {{command|pungi}} when creating installable media (see [[How_to_build_a_Rawhide_ISO_image_for_testing|instructions]])
+# {{filename|compose-tree}} script - Script that creates a mock chroot and creates install images using {{command|pungi}} (see also [[How_to_build_a_Rawhide_ISO_image_for_testing|instructions]])
 # {{filename|tests/rats_install/install.py}} - AutoQA test script that does a basic automated kickstart install
-= Project Ideas =
+== Project Ideas ==
-== Update AutoQA storage unit testsuite ==
+=== Update AutoQA storage unit testsuite ===
 ; Scope
-: The patchset in the ''clumens'' autoqa branch may need to be refreshed to ''master'' and re-run to check for proper operation.
+: 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''
-== Integrate checkbot.sh with AutoQA ==
+=== Integrate checkbot.sh with AutoQA ===
-== Automate Installation test matrix ==
+; Scope
+: Currently, anaconda-devel uses a script called {{filename|checkbot.sh}} to run {{command|pylint}} and {{command|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''
+=== Create post-git-commit AutoQA hook ===
+; Scope
+: To support triggering tests based on git commits, create a new AutoQA watcher.
+; Skill Level
+: Moderate
+; Owner
+: ''unassigned''
+=== Automate Installation test matrix ===
 ; Scope
 : Automate installation test matrix (see [[Is_anaconda_broken_proposal]])
+; Skill Level
+: Advanced
+; Owner
+: ''unassigned''
+=== New post-koji-build test to run pungi ===
+; Scope
+: Create a new [[AutoQA]] test using the {{filename|compose-tree}} script that runs pungi inside a mock chroot.  This test is intended to run after a koji build of {{package|anaconda}} or it's dependent packages.
+; Skill Level
+: Moderate
+; Owner
+: ''unassigned''

Search