James Laska wrote:
Greetings,
Bill and I discussed this a bit on IRC. I thought I'd bring it to the
list as well.
Ray Chen joined fedora-test-list recently and noted interest in
contributing to the beaker project in his introduction. Bill and I
discussed some topics that might be good things to get started for new
recruits. Some ideas include ...
* Packaging assistance with beaker/medusa? -
https://fedorahosted.org/beaker
* Packaging and seeking review for rhtslib (as beaker-testlib?) -
https://fedorahosted.org/beaker/wiki/RHTSLibrary
* Setup and host a demo instance (via fedora-infrastructure
guest)?
* Wiki doc help?
* Writing built-in unit tests?
What other areas might be good for folks to help contribute today?
* Define the interfaces between the Lab Controller and the test server.
* Define and design the test execution controller
- This will be similar to the STAF STAX service (which is Java + XML)
- This needs to be done before anything useful can be done for rhtslib
- Once it's defined you can implement the STAF side of it before the
LC side is implemented
rhtslib really needs to be done as a STAF service, but you won't know how
to do it until the execution controller (EC) is defined. The EC needs to
be able to take in a recipe, provision test servers, run tests and collect
results. It really is the linchpin of the whole system and writing any
test code at this point is pretty much wasted effort IMHO.
I'd have simply gone with STAX as the execution controller, but I've heard
horror stories about it ... and it's Java :)
Cheers, Jeff.
--
Jeff Fearn <jfearn(a)redhat.com>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY