AutoQA

Project Name

AutoQA

Project Description

AutoQA is an automated test system for Fedora. when certain events occur, AutoQA launches automated tests. At present there are event watchers for koji builds, bodhi updates, repo changes, and nightly installed images; these events trigger a small number of tests, but more tests are needed.

Project Leader(s)

Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki

Project Contributor(s)

Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki

NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.

Project Details

AutoAQ uses Autotest client codes for common utility. The testing execution engine consists of it's own codes to control flow and some autotest codes. The test script repository is not large enough, right now only have these test cases: anaconda, conflicts, depcheck, initscripts, rats_install, rats_sanity, repoclosure, rpmguard, and rpmlint

Project Plan

Goals for each release:

• 0.1 bite-sized initial project (Nov 12)
• 0.2 cleanup-refinement
• 0.3 New test or extending features

Project News

This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.

Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.

Learning subjects

- Git

- Python

Resources

- James Laska

- AutoQA mailing list

- Chris Tyler

Background to AutoQA

Discussed general design and goals for the AutoQA project (http://fedoraproject.org/wiki/AutoQA).

Question - is autoqa integrated with koji/bodhi? Answer - not integrated, but monitors for koji/bodhi events. autoqa is running in hardware inside Fedora infrastructure, but not yet packaged for fedora due to missing Java dependencies

Question - is autoqa polling to look for work? Answer - yes, right now the "hooks" monitor for test events (such as koji or bodhi builds)

What needs to be done

• Future test cases are recorded in TRAC at https://fedorahosted.org/autoqa/milestone/Future%20test%20cases
• Simple web front-end for our ResultDB
• Finishing some of half-baked tests: Package Sanity Test, Rpmlint whitelisting

• Sample bite-sized tests to consider
  • Creating autoqa wrapper for man-page checker (https://fedorahosted.org/autoqa/ticket/197)
  • Font-lint (https://fedorahosted.org/autoqa/ticket/92)
  • Automate fedora package acceptance (https://fedorahosted.org/autoqa/ticket/218)
  • Test for un-owned directories (https://fedorahosted.org/autoqa/ticket/31)
  • ABI validator (https://fedorahosted.org/autoqa/ticket/190)
• Larger possibilities
  • systemd tests (similar to http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=tests/initscripts;)

Rough plan for getting it done

• don't be afraid to ask any question on autoqa-devel ML (join that list!)
  • https://fedorahosted.org/mailman/listinfo/autoqa-devel
• contacts: jlaska, kparal, wwoods, jskladan on #fedora-qa IRC channel
• read https://fedoraproject.org/wiki/AutoQA
• ctyler to meet with students to discuss divvy-up of first-step tests

Attendees

• James Laska (jlaska) - Fedora QA
• Jaewoo Park(jwpark2)
• Chris Tyler (ctyler)
• Kamil Paral (kparal) - Fedora QA
• Eric Shum (escom)
• Hoc Tran (hvtran)

AutoQA Startup Meeting Phone call 2010-11-03 (will be recorded)

* 800-451-8679 (conf# 684-645-9442)
http://typewith.me/fBktOsdjk9