I spoke to jforbes yesterday and we discussed challenges with previous virtualization test events (details available in pages linked from https://fedoraproject.org/wiki/Category:QA_Retrospective). Jforbes is pulling together some content soon. If we can try to limit testing to 3 focus areas, perhaps that might be a good strategy. Something like ... 1) Virtualization core (basics of booting/installing guests of different arch/OS/release? 2) Some new feature, 3) Some other feature. Just a thought to avoid too much choice.

Also, instead of a table listing all possible test cases, perhaps the "What worked" and "What doesn't work" approach would be more suitable.

I've added below cases to the [https://fedoraproject.org/wiki/Test_Day:2011-04-14_Virtualization#Testing Test day page] with the help of lib-virt qe team:

Spice[[BR]]

• QA:Testcase Virtualization Check SPICE password support
• QA:Testcase Virtualization Manually set spice listening port with TLS port set
• QA:Testcase Virtualization Setting up a VM with Spice
• QA:Testcase Virtualization Spice listen on all public network interfaces

libvirt[[BR]]

• QA:Testcase Virtualization libvirt create a logical pool
• QA:Testcase Virtualization libvirt save and restore with svirt
• QA:Testcase Virtualization libvirt set guest memory

Hotplug[[BR]]

• QA:Testcase Virtualization Attach/Detach a SCSI device to guest
• QA:Testcase Virtualization Hotplug USB device to guest
• QA:Testcase_Virtualization_NIC_Hotplug_virsh_attach_detach

Besides, I modified the 'testing' part to link to cases directly, also deleted some to make the number of tests suitable for one day. Feel free to add/del the cases as you need. But I think the number of total cases should be no more than this. [[BR]]

Please send out the announcement once you are satisfied with it. Thanks

Completed, closing ticket.