From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 3: | Line 3: | ||
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_17_test_days]] | | image = [[File:Echo-testing-48px.png|link=QA/Fedora_17_test_days]] | ||
| caption = GNOME Boxes | | caption = GNOME Boxes | ||
| date = 2012-05- | | date = 2012-05-10 | ||
| time = all day | | time = all day | ||
| website = [[QA/Fedora_17_test_days]] | | website = [[QA/Fedora_17_test_days]] | ||
| Line 14: | Line 14: | ||
== What to test? == | == What to test? == | ||
Today's instalment of Fedora Test Day will focus on Gnome Boxes | Today's instalment of Fedora Test Day will focus on Gnome Boxes. | ||
== Who's available == | == Who's available == | ||
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:zeenix|Zeeshan Ali]] (zeenix), [[User:Jwrdegoede|Hans de Goede]] (hansg), [[User:teuf|Christophe Fergeau]] (teuf) | * Development - [[User:Developer2|Developer2]] (irc_nick2), [[User:zeenix|Zeeshan Ali]] (zeenix), [[User:Jwrdegoede|Hans de Goede]] (hansg), [[User:teuf|Christophe Fergeau]] (teuf) | ||
* Quality Assurance - [[User:Martix|Martin Holec]] (Martix), [[User:Adamwill|Adam Williamson]] (adamw), [[User:pschindl|Petr Schindler]] (pschindl) | * Quality Assurance - [[User:Martix|Martin Holec]] (Martix), [[User:Adamwill|Adam Williamson]] (adamw), [[User:pschindl|Petr Schindler]] (pschindl) | ||
== Prerequisite for Test Day == | == 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 | * 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 [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image] | ||
* | * Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions] | ||
== How to test? == | == 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 [[Releases/Rawhide|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 [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ 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 == | == Test Results == | ||
If you have problems with any of the tests, report a bug to [https://bugzilla. | 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 [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility 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 [[Template:result|result template]] to enter your result, as shown in the example result line. | |||
{| | {| | ||
! User | ! User | ||
! Smolt Profile | ! Smolt Profile | ||
! [[QA: | ! [[QA:Testcase_sample_1|Sample test 1]] | ||
! [[QA: | ! [[QA:Testcase_sample_2|Sample test 2]] | ||
! [[QA: | ! [[QA:Testcase_sample_3|Sample test 3]] | ||
! [[QA: | ! [[QA:Testcase_sample_4|Sample test 4]] | ||
! References | ! References | ||
|- | |- | ||
| Line 85: | Line 102: | ||
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW] | | [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | ||
| {{result|fail}} <ref>{{bz|12345}}</ref> | | {{result|fail}} <ref>{{bz|12345}}</ref> | ||
| <references/> | | <references/> | ||
|- | |- | ||
|} | |} | ||
[[Category:Test Days]] | |||
[[Category:QA Templates]] | |||
[[Category: | |||