On Wed, 26 Oct 2011 09:55:45 -0400 (EDT)
Kamil Paral <kparal(a)redhat.com> wrote:
The 'capture bodhi comments' feature is just great, great
job, Tim.
What features do you expect to have mocked in the future for Koji?
The idea is to eventually have a method for running functional tests
against AutoQA, so enough to be able to do that. I've listed my current
plans below but that all could change. I should probably take some time
to better document what I'm planning.
If anyone has suggestions or ideas, I'm open to them. This is more of a
"vague plan in Tim's head" right now than anything formal.
How soon would all of this be ready? Not sure, depends on how this all
fits in with our other priorities. For now, I'm mostly interested in
getting 0.7.0 out the door soon after F16 release (and getting F16 out
the door, obviously).
Tim
Currently Planned Features:
- rpm and repo generation
* Basically, read in a description file of rpm metadata that would
be used to create "fake" rpms w/ rpmfluff
* Generate repos and koji metadata for those "fake" rpms
* Need to figure out some sort of description format for the
repos/rpms
- Multiple operation modes
* Just capturing comments
* Full Mock (artifical RPMs, Repos, Koji)
- Remote interface
* Allow for environment setup and change detection
* In support of running automated functional tests
bojiClient.setupEnv('some_env')
schedule_autoqa()
bojiClient.getChanges() // this may end up being more resultsdb
check_changes()
NTH Maybe Features:
- Environment Capture
* Debugging AutoQA issues can be a real pain since the data we
depend on is so volatile
* The idea would be to pass in job data and get a reproducible
environment for a failure
* Not sure it'll be worth the time and effort to make this work,
though.
- Better GUI
* yeah, the current one works but it isn't the prettiest or most
usable thing ever.