Test Day:2012-05-17 Gnome Boxes
|Fedora Test Days|
|Mail • Subscribe • Archives|
What to test?
Today's instalment of Fedora Test Day will focus on Gnome Boxes.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Zeeshan Ali (zeenix), Hans de Goede (hansg), Christophe Fergeau (teuf)
- Quality Assurance - Martin Holec (Martix), Adam Williamson (adamw), Petr Schindler (pschindl)
Prerequisite for Test Day
- Free space on HD
- Various operating systems installation ISOs, CD/DVDs and USB sticks:
- Fedora 16 and 17
- Windows XP and 7
- Debian, Ubuntu etc.
How to test?
Install latest Fedora 17 prerelease
Install Gnome Boxes
Install Gnome Boxes by running: yum install libvirt gnome-boxes on installed system.
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.
- 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.
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|