From Fedora Project Wiki
m (Add data mining) |
(Add color) |
||
| Line 20: | Line 20: | ||
: 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. | : 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 | ; Skill Level | ||
: Advanced | : <span style="color:red;font-weight:bold;">Advanced</span> | ||
; Owner | ; Owner | ||
: ''unassigned'' | : ''unassigned'' | ||
| Line 29: | Line 29: | ||
: 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. | : 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 | ; Skill Level | ||
: Beginner | : <span style="color:green;font-weight:bold;">Beginner</span> | ||
; Owner | ; Owner | ||
: ''unassigned'' | : ''unassigned'' | ||
| Line 39: | Line 39: | ||
: 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. | : 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 | ; Skill Level | ||
: Moderate | : <span style="color:orange;font-weight:bold;">Moderate</span> | ||
; Owner | ; Owner | ||
: ''unassigned'' | : ''unassigned'' | ||
| Line 48: | Line 48: | ||
: To support triggering tests based on git commits, create a new AutoQA watcher. | : To support triggering tests based on git commits, create a new AutoQA watcher. | ||
; Skill Level | ; Skill Level | ||
: Moderate | : <span style="color:orange;font-weight:bold;">Moderate</span> | ||
; Owner | ; Owner | ||
: ''unassigned'' | : ''unassigned'' | ||
| Line 57: | Line 57: | ||
: Automate installation test matrix (see [[Is_anaconda_broken_proposal]]) | : Automate installation test matrix (see [[Is_anaconda_broken_proposal]]) | ||
; Skill Level | ; Skill Level | ||
: Advanced | : <span style="color:red;font-weight:bold;">Advanced</span> | ||
; Owner | ; Owner | ||
: ''unassigned'' | : ''unassigned'' | ||
| Line 66: | Line 66: | ||
: 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. | : 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 | ; Skill Level | ||
: Moderate | : <span style="color:orange;font-weight:bold;">Moderate</span> | ||
; Owner | ; Owner | ||
: ''unassigned'' | : ''unassigned'' | ||
Revision as of 20:45, 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.
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- 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 theclumensbranch of autoqa.gitcompose-treescript - 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
- unassigned
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.shto runpylintandmakeagainst 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)
- Skill Level
- Advanced
- Owner
- unassigned
