Chinaunix首页 | 论坛 | 博客
  • 博客访问: 451956
  • 博文数量: 45
  • 博客积分: 2526
  • 博客等级: 少校
  • 技术积分: 478
  • 用 户 组: 普通用户
  • 注册时间: 2008-05-12 21:04










2010-06-10 16:32:10

I have followed up some Feodra QA projects for long time, since actually I have
been working as Testing Automation Engineer. There are some tools in Fedora QA
projects, such as beaker and autoqa. The latter one is under heavy development
recently, because there are lots of existing testing cases needed to integrate.
Any way, both tools are NOT in stable model. So, don't consider to use them in
real testing machine until it's stable. However, the design method is charming
and easy to understand. If you are interested with automation tools, just see
the following words:)

1. AutoQA
As the wiki says, autoqa is a automated testing system for Fedora. The overview
info can be found here:

As we know, test harness is cpnsisted of test exexution engine and test script
repository. Here, autoqa use client codes for common utility. The
testing execution engine is consisted 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  rpmlint

Take for example, The goal of these tests is to check LSB compliance
of initscripts. The logical is not hard and easy to read. It use as
backend. Beakerlib is a shell-devel integration testing library. You can easily
use 'yum install beakerlib' to install it.

And in bakerlib package, there are some example scripts to help you quickly learn.
it's a good start guide for advanced shell program.

For more autoqa development detail, please read these two mailinglist:

2. beaker
This project is also testing automated system, including hardware setup, OS
batch installtion, software deploy and test schedule, as well as test harness.
We can see that beaker can help uses to setup lab testing environment, and
than use some test harness (such as autoqa ) to do scheduled job. More design
docs are located:

what's more, there will be a public website to show testing result from beaker.

This system may be like the waterfall of buildbot.

This project is under construction in redhat community. Even if I'm member of
beaker project, I still find it's hard to set up the testing environment and
contribute more codes. Because it needs some testing machines and good understand
of testing flow in redhat company which maybe is commerce secret.

That's all, welcome comments:)

阅读(4804) | 评论(3) | 转发(0) |

chinaunix网友2010-06-11 20:09:06

Hi Ray! Yes, it's jlaska :) I admit, I needed help from google translate to know which buttons to click!

crook2010-06-10 22:30:11

I guess you are jlaska:). thanks for commnets. I really got a big surprise that you can add comments in this chinese website!

chinaunix网友2010-06-10 22:07:50

Great post! I wanted to point out a minor correction. The proposal you mention is intended as a stand-alone test suite. It currently is executed inside the AutoQA framework, but like any test suite, there's no reason it couldn't be integrated into any other test harness. You might also be interested in the the work Liam Li is doing to build an automated installer test suite. For details, see