# AutoQA priority discussion
# Date: 2010-06-09
# Time: 14:00 UTC (10:00 EDT, 15:00 CEST)
# Attendees: kparal, jskladan, wwoods, jlaska
Several folks working toward the Package Update Acceptance test plan met
and discussed re-prioritizing outstanding tasks. Below are the notes
from that meeting.
== Agenda ==
Mindmap:
http://kparal.fedorapeople.org/autoqa/tasks.png
== Conclusions ==
* Focus on infrastructure/architecture parts first
* testing autotest-server instance important, publicly available
instance not so important
* Current high priority tasks:
* post-bodhi-hook
* feature-complete, needs to be tested and merged into master
* resultdb
* quick version of virt support
* getting public accessible machines
* public autotest blocked on packaging gwt + deps (java booooo)
* Lower priority tasks
* Package sanity tests
* Package update tests
* Initscripts
* message bus (aka "pony")
* full virt support (destructive tests)
* depcheck (permissive vs enforcing)
* unit testing of koji/bodhi libraries
* requires test data stored in koji & bodhi
== TODO ==
* [jlaska] find a machine where resultdb may run (it can be VM, publicly
accessible preferred)
* [jlaska] set up testing instance of autotest-server
* [kparal] implement *quick* virtualization support
* [jskladan, wwoods helping] bodhi hook needs to be tested
* [jskladan, kparal, wwoods] continue implementing and testing resultdb
== Dependencies ==
-> testing instance of autotest-server -> bodhi hook testing -> add
support for our tests
-> testing instance of autotest-server -> quick virtualization support
-> (publicly accessible) machine -> resultdb efforts
== Next Meeting ==
* 2010-06-25 - Check-in on autoqa-devel@ for status on action items