From Fedora Project Wiki

No edit summary
Line 58: Line 58:


Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category: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]].
* [[QA:Testcase Gnome Boxes manual installation]]
* [[QA:Testcase Gnome Boxes express installation]] (unattended installation)
* [[QA:Testcase Gnome Boxes basic usage]]
* [[QA:Testcase Gnome Boxes box configuration]]
* [[QA:Testcase Gnome Boxes box removal]]


* Next would be box creation. This will involve:
* Next would be box creation. This will involve:
Line 64: Line 71:
is chosen, no user interaction should be needed. BTW, unless hosts are
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.
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:
* Once we have some boxes, we can test using of those boxes:

Revision as of 16:39, 10 May 2012

Fedora Test Days
GNOME Boxes

Date 2012-05-17
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 ...

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

Verification
Please check the SHA256SUM is correct before booting!
Architecture SHA256SUM
x86_64 9bac97cf38366b881fd8a1c988e49e4d1e1b4184649a6a77d61d72bd7543a7eb
i386 ec5ff25676c0d5385e4e882244a1d3cc14a819bd1d461c48d08cfb28561aff4a
Hardware profile
Update system
  • After you install Fedora 17 prerelease, make sure you have all the current updates for it installed, using the update manager or running yum update on installed system.

Install Gnome Boxes

Install Gnome Boxes by running: yum install libvirt gnome-boxes on installed system.

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.


  • 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.

  • 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.

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 pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345