On Fri, 2010-03-26 at 09:48 -0400, Bill Peck wrote:
Just fleshing out some ideas on how Beaker may work with Fedora.
Remember this is not a replacement for autoQA, Beaker is about finding
the hardware described in the test plan, provisioning the distro under
test, adding any additional packages, and finally running the tests.
The final part is done by the harness which could be beah (Beaker
Harness) or autotest.
This is a great milestone, congrats Bill and team!
Looking at the road map below there are more questions then answers.
But we have to start somewhere. :-)
Fedora Beaker test road Map
----------------------------------------------------
* Package Review (waiting on reviewer)
* Proof of concept Deployment (to be done by bpeck after package review)
* Meet with Fedora Infrastructure on how to deploy in Fedora space.
* Who will admin the software of the Fedora instance (bpeck most likely)
* What hardware will be added?
* What tests to deploy?
* Who will run and review the tests?
These last 2 points, I'd recommend keeping them very small and focused.
Something specific ... a class of kernel tests etc... Some other
thoughts ...
* Where to store the tests? This is more long-term for after the
first tests have been piloted ... but should we use CVS Dist
etc. We have tests in AutoQA now, but I'm open to another
mechanism more closely coupled with the packages themselves.
Just need to document it.
* Once we know what tests are desired ... we can use AutoQA to
schedule your beaker jobs. Just need to know what hook/event
you'll need to schedule your tests (koji build, bodhi update,
cvs commit etc...) -
https://fedoraproject.org/wiki/Writing_AutoQA_Hooks
Thanks,
James