Editing Test Day:2012-03-15 Gnome Shell and Extensions

{{autolang|base=yes}}

{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_17_test_days]]
| caption = gnome-shell and extensions
| date = 2012-03-15
| time = all day
| website = http://extensions.gnome.org/
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
}}

{{admon/note | 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 [http://bugzilla.gnome.org GNOME 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 [[QA/Test_Days|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-shell extension management. Since the release of GNOME 3 about a year ago there's been a great progress in ways one can customize it. Remember applets, desktop widgets etc. back in GNOME 2? Missed them? Now we have all that back in form of gnome-shell extensions! Shell's architecture makes it relatively painless to make them and lots of useful extensions are already out.

There are several ways one can manage gnome-shell extensions. In addition to having gnome-tweak-tool, extension management has also been integrated with Firefox and https://extensions.gnome.org/, where you can search for and install extensions as well as enable/disable them. Haven't tried it yet? Go on, it's really nice! And while you're at it, please help us test these various ways of extension management by following the few test cases over here, catching bugs and thus contributing in efforts of making gnome-shell with extensions what all have been waiting for!

[[File:shell-extensions.png|500x282px]]

== Who's available ==

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ... (to be negotiated)
* Development - [[User:Mclasen|Matthias Clasen]] (mclasen)
* Quality Assurance - [[User:Adamwill|Adam Williamson]] (adamw), [[User:Vhumpa|Vítězslav Humpa]] (vhumpa)

== Prerequisite for Test Day == 

* An updated [http://fedoraproject.org/get-prerelease Fedora 17 pre-release], or the [[#Live_image|specific Test Day live image]].
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]

* For most testing, a graphics adapter capable of compositing. If you have an adapter that doesn't support HW acceleration, you can still proceed if the all new software rendering kicks in. However you can still expect frequent lags and crashes, especially if you're having software rendering due to running Fedora in virtual environment.

{{admon/important|Shell inside VirtualBox or virt-manager / KVM|Until now only modern and 3D capable cards were able to run gnome-shell. Most modern CPUs are in principle powerful enough to run gnome-shell and a full GNOME 3 session without 3D support and only via software rendering. Thanks to updates in several packages software rendering will be available from Fedora 17. This means that a full desktop session can now be run inside VMs as well using vesa, cirrus or qxl drivers. If it's inconvenient for you to install Fedora or use the Live CD on 'real' HW, you can take advantage of VMs. However be warned that you are still likely to experience frequent crashes at this point, which is why the next Gnome Test Day will focus on software rendering. If you can, please join us then as well: [[Test_Day:2012-03-29 Gnome Shell Software Rendering|2012-03-29]]}}

<!-- Also helpful, if you have or can get them:

* Additional displays (monitors, TVs...)
* Optical media (burned, commercially pressed, and blank burnable, CDs, DVDs and Blu-Rays)
* Wi-fi/bluetooth enabled networking devices
* Graphics adapters, virtual machines, or driver configurations not capable of compositing, to test fallback support (see below) -->

== How to test? ==

=== Live image ===

{{admon/important|Verification|Please check the SHA256SUM is correct before booting!}}

You may download a non-destructive pre-Fedora 17 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].

{|
!colspan=1|Architecture !! SHA256SUM 
|- 
| <!-- [http://adamwill.fedorapeople.org/gnome3-test-20110421/gnome-20110419-i686.iso i686] || <code>9af0d24337a435d9c3f10fb34d1f16af7d6496b10ca0facf1a0630b45a66d544</code> -->
|-
| <!-- [http://adamwill.fedorapeople.org/gnome3-test-20110421/gnome-20110419-x86_64.iso x86_64] || <code>7d69f8324afc3de809144ff4104879c2240f3017e4db84cf5ed0d0259abb83e1</code> -->
|-
|}

<!--
'''Post-live image updates'''

The following updates that fix known bugs are available beyond what is included in the live image:

* [http://koji.fedoraproject.org/koji/buildinfo?buildID=216936 control-center-2.91.6-4.fc15] - fixes a crash on running the '''Region and Language''' configuration panel, and the '''Date and Time''' panel
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=216924 gnome-bluetooth-2.91.5-4.fc15] - fixes a crash on running the '''Bluetooth''' configuration panel
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=216898 gnome-shell-2.91.6-4.fc15] - fixes the bluetooth system icon not appearing: {{bz|674874}}
-->
Using the live image is the easiest way to participate in testing for most people, but alternatively you can:

=== Update your machine to Fedora 17 ===

If you are already running or want to try the pre-release of Fedora 17, [http://fedoraproject.org/get-prerelease install Fedora 17 Alpha] and then update to the latest packages. <!-- As of 2011-04-20, all the necessary packages for the Test Day should be available in the ''fedora'' or ''updates-testing'' repositories.--> '''Using the live image is easier and highly recommended'''.

== Perform testing ==

Please perform as many of the test cases listed as you have the time and the resources to complete, and fill out your results in the table below. You do not need a Fedora account to fill in the table.

<!-- {{admon/warning | Network configuration problems | GNOME 3's network configuration interface is not yet feature complete and cannot handle some cases that GNOME 2's could. If a feature you need to set up your network is missing, use the {{command|nm-connection-editor}} tool. See [[Common_F15_bugs#networkmanager_shell|this Common Bugs entry]] for more details.}} -->

=== Fallback  ===

If you are unable to run a full GNOME 3 session either through HW or SW rendering and fallback mode kicks in you won't be able to run gnome-shell and any of its extensions. In this case, please, don't hesitate to ask on IRC as there might be a way we can help you start a regular session.

=== Regular tests ===

<!-- * [[QA:Testcase_gnome-shell_dash]]
* [[QA:Testcase_gnome-shell_workspaces]]
* [[QA:Testcase_gnome-shell_overview_search]] -->

* [[QA:Testcase_gnome-shell_extensions_install]]
* [[QA:Testcase_gnome-shell_extensions_tweak_tool]]
* [[QA:Testcase_gnome-shell_extensions_firefox]]
* [[QA:Testcase_gnome-shell_extensions_remove]]

=== Unplanned testing ===

As well as running the formal test cases, you can help simply by running gnome-shell and reporting any problems you come across in the course of your typical usage of extensions, even if this does not match up with any of the test cases. If you are unsure to what any discovered problem relates, please check in [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] before you file a bug.

<!--
'''NOTE''': There are [http://koji.fedoraproject.org/koji/buildinfo?buildID=216849 updated control-center packages] if you experience crashes in the "Region and Language" panel -->

== Test Results ==

If you have problems with any of the tests, try and report a bug. Most bugs in this event should be reported to [http://bugzilla.gnome.org GNOME Bugzilla]. Bugs that are clearly issues in Fedora GNOME integration should be reported to [http://bugzilla.redhat.com Fedora Bugzilla]. You will need an account to report bugs, but creating one is easy, and we will help you do this if you ask in [irc://irc.freenode.net/#fedora-test-day IRC]. 

If you are not sure of the appropriate component, please check in [irc://irc.freenode.net/#fedora-test-day IRC] before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on [irc://irc.freenode.net/#fedora-test-day 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. If you are running Fedora in VM, please, at least state the name of VM hypervisor(kvm/VirtualBox...). For each test case, use the ''result'' template to describe your result, following the examples in the ''Sample user'' row.

{|
! User
! Smolt Profile
! [[QA:Testcase_gnome-shell_dash|Dash]]
! [[QA:Testcase_gnome-shell_workspaces|Workspaces]]
! [[QA:Testcase_gnome-shell_overview_search|Search]]
! References
|-
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| {{result|pass}} 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
|-
! User
! Smolt Profile
! [[QA:Testcase_gnome-shell_dash|Dash]]
! [[QA:Testcase_gnome-shell_workspaces|Workspaces]]
! [[QA:Testcase_gnome-shell_overview_search|Search]]
! References
|}


[[Category:Fedora 17 Test Days]]