Difference between revisions of "AutoQA"
| Line 33: | Line 33: | ||
* 0.2 Draft of New test or extending features | * 0.2 Draft of New test or extending features | ||
| − | + | Creating autoqa wrapper for man-page checker (https://fedorahosted.org/autoqa/ticket/197) : Jaewoo Park | |
* 0.3 New test or extending features working smoothly | * 0.3 New test or extending features working smoothly | ||
Revision as of 17:59, 9 November 2010
Contents
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 Member(s)
Eric Shum, Hoc Tran, Rizwan Haq, Jaewoo Park
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 AutoQA and Autotest server and client setting (Nov 12)
- 0.2 Draft of New test or extending features
Creating autoqa wrapper for man-page checker (https://fedorahosted.org/autoqa/ticket/197) : Jaewoo Park
- 0.3 New test or extending features working smoothly
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
