Test Day:2012-05-17 Gnome Boxes

Fedora Test Days
GNOME Boxes
Date	2012-05-10
Time	all day
Website	QA/Fedora_17_test_days
IRC	#fedora-test-day (webirc)
Mailing list	test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on Gnome Boxes.

Who's available

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

• Development - Developer2 (irc_nick2), Zeeshan Ali (zeenix), Hans de Goede, Christophe Fergeau (teuf)
• Quality Assurance - Martin Holec (Martix), Adam Williamson (adamw), Petr Schindler (pschindl)

Prerequisite for Test Day

List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?

• Usb key
• Usb externally connected HD IDE/SATA
• Empty HD IDE/SATA/SCSI
• Free space on HD

Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:

• An updated Fedora XX pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
• Your hardware profile uploaded to Smolt according to these instructions

How to test?

Here is a few things we should do during the testing:

• Make sure QA starts from a clean slate. i-e An up2date F17 machine w/o

gnome-boxes installed. They start by installing gnome-boxes..

• Having said that, they should have different installer ISOs (Fedora 16

and 17, Windows XP and 7, latest Ubuntu, Debian etc) in a standard location (~/Downloads is the obvious choice here). They probably also want to have one or two hardware installer medias (USB stick and/or CDROM with an ISO written on them) handy as well.

• Next would be box creation. This will involve:
• VM boxes: Create boxes for various OSs w/ and w/o express

installation and see if it goes as expected. When express installation is chosen, no user interaction should be needed. BTW, unless hosts are very powerful, I suggest not having more than 2 boxes running at a time.

• remote boxes: For this we'll need a/few remote machine(s) with

SPICE and/or VNC enabled.

• Once we have some boxes, we can test using of those boxes:
• Selecting them should bring them up, then you do random things

inside the guests (e.g browsing network, watching some media clip etc).

• maximized and unmaximized (resize window).
• windowed and fullscreened.
• Going into and out of the box.

• Checking the properties view would be next. See if the properties are

not lying and fiddle with the modifiable properties.

• Then is selection view and box deletion. Check if box is actually

deleted by quitting boxes after deleting and starting it again (deleted box should be gone). Test if cancellation of box deletion also works as expected.

Update your machine

If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image

Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.

Test Cases

Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

User	Smolt Profile	Sample test 1	Sample test 2	Sample test 3	Sample test 4	References
Sample User	HW	none	pass	warn	fail