From Fedora Project Wiki
(Initial page) |
|||
Line 22: | Line 22: | ||
: <span style="color:red;font-weight:bold;">Advanced</span> | : <span style="color:red;font-weight:bold;">Advanced</span> | ||
; Owner | ; Owner | ||
: | : [[User:Clumens|Chris Lumens]] | ||
=== Create a bugzilla query (or script) to identify storage unit testsuite candidates === | === Create a bugzilla query (or script) to identify storage unit testsuite candidates === |
Revision as of 20:47, 15 November 2010
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- Build test - runs
./autogen.sh && ./configure.sh && make
- Pylint test - Runs
tests/pylint/runpylint.sh
- Build test - runs
tests/anaconda_storage
- Storage unit testsuite in theclumens
branch of autoqa.gitcompose-tree
script - Script that creates a mock chroot and creates install images usingpungi
(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
- Chris Lumens
Create a bugzilla query (or script) to identify storage unit testsuite candidates
- Scope
- Work with anaconda-devel to identify a pattern to identify bug reports that may have traceback information that can be used to craft new storage unit tests. This task does not involve creating the tests, only identifying a bugzilla query or script that can query bugzilla for test candidates.
- Skill Level
- Beginner
- Owner
- unassigned
Create AutoQA test based on checkbot.sh
script
- Scope
- Currently, anaconda-devel uses a script called
checkbot.sh
to runpylint
andmake
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 AutoQA post-git-commit watcher
- 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). This is definitely not a short-term deliverable, and is dependent on several tasks already on this page. Open to additional suggestions/ideas on short-term tasks that are in line with this larger goal.
- Skill Level
- Advanced
- Owner
- unassigned
Create AutoQA test based on compose-tree
script
- 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 ofanaconda
or it's dependent packages. - Skill Level
- Moderate
- Owner
- unassigned
Verify RHBZ #576439 and integrate VirtIO into rats_install test
- Scope
- With RHBZ #576439, we now can monitor installation progress without requiring an active network to transmit logs using minimon. Installing without networking allows test automation that more accurately mimics non-network installations. This task involves testing RHBZ #576439 to confirm that the required support exists as well as updating
rats_install/install.py
to use virtio for installation progress monitoring. - Skill Level
- Moderate
- Owner
- newgle1