From Fedora Project Wiki

Line 21: Line 21:
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Markmc|Mark McLoughlin]], [[User:Rjones|Rich Jones]], [[User:Berrange|Dan Berrange]]
* Development - [[User:Markmc|Mark McLoughlin]], [[User:Rjones|Rich Jones]], [[User:Berrange|Dan Berrange]]
* Quality Assurance - [[User:jlaska|James Laska]]
* Quality Assurance - [[User:jlaska|James Laska]], [[User:cward|Chris Ward]]


=== Prerequisite for Test Day ===
=== Prerequisite for Test Day ===

Revision as of 11:02, 29 April 2009

DATE TIME WHERE
Thu May 7, 2009 All Day #fedora-qa)

What to test?

Today's installment of Fedora Test Day will focus on widespread testing of Fedora Virtualization in general, with a particular emphasis on some:

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

You will primarily be concerned with testing Fedora 11 as a virtualization host. You will need:

  • A fully updated Fedora 11 Rawhide machine. For information on installing and upgrading to rawhide, see Releases/Rawhide.
  • Hardware virtualization support (e.g. Intel VT or AMD-V). If not, you can still help with testing QEMU support.
  • At least one guest image installed before the test day.
  • Up to 10-20Gb free disk space. Guest images take up a lot of space.
  • To test device assignment, Intel VT-d or AMD IOMMU support.
  • To test kvm-autotest, DVD ISOs downloaded for Fedora 8
  • To test Fedora 11 guest installs, DVD ISOs downloaded for Fedora 11 Preview Release

How to test?

Jump on IRC, pick some areas to test from the table below, add yourself to the table and file bugs as you see them.

Coming soon ...
Stay tuned for test cases for each of the test areas.
Test Area Comments Testers Required Estimated Time Testers Status
Device Assignment Requires specific hardware (i.e. VT-d) 2 2 hours Mark McLoughlin Not started
sVirt Some familiarity with SELinux would help 4 2 hours Dan Walsh, Martin Koci Not started
VNC Authentication SASL authentication in VNC qemu server; several auth methods need testing 2 2 hours Dan Berrange Not started
Graphical Console F11 guests should have 1024x768 and absolute pointer by default 2 30 minutes Rich Jones Not started
KVM Test Suite We want to have kvm-autotest run on as many different hardware profiles as possible 10 30 minutes Mike Burns Not started
libvirt Basic libvirt acceptance testing 4 30 minutes Dan Berrange, Rich Jones Not started
virt-install Guest installs from command line 2 2 hours Cole Robinson Not started
virt-manager Broad coverage of all virt-manager functionality 4 4 hours Cole Robinson Not started
Guest Installs F10, F11, RHEL 3/4/5 and Windows installs 4 2 hours Liam Li Not started
Device Hotplug Testing both hotplug UI and underlying KVM/QEMU support 2 2 hour Marcelo Tosatti Not started
SMP and CPU Hotplug Testing basic SMP support; also CPU hotplug from UI 2 2 hours Glauber Costa Not started
Save/Restore/Migrate Remote migration needs a second machine, basic testing possible without this 2 2 hours Glauber Costa Not started
Suspend/Resume/Shutdown/Reboot Important to test with different Guest OSes 2 2 hours Marcelo Tosatti Not started
Console Including graphical/serial, scaling, fullscreen, grabs, keymaps 4 2 hours Dan Berrange Not started
Networking Different host network configurations, different NICs 2 2 hours Mark McLoughlin Not started
Storage Different storage pools, image formats, virtio/ide/scsi, caching modes 2 4 hours Dan Berrange Not started
Xen DomU Need to ensure that F11 works well as a Xen guest 2 2 hours Chris Lalancette Not started