From Fedora Project Wiki
(Created page with "{{QA/Test_Case |description= extensions.gnome.org management |setup= {{Testcase_gnome-shell_generic_setup}} # Make sure you have {{package|gnome-tweak-tool}} installed using {{pa...") |
No edit summary |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description= extensions.gnome.org management | |description=This test case aims at extensions.gnome.org extension management made available in your favourite browser by ''Gnome Shell Integration'' plugin. | ||
{{admon/important|Firefox GNOME Shell integration misbehaving| | |||
In current Fedora 17, there are problems with the gnome-shell integration. Most often Firefox won't "''see''" any extensions, available as well as already installed. If this happens to you, please, install (''su -c 'yum install '''epiphany'''' '') epiphany to do the rest of testing.}} | |||
|setup= | |setup= | ||
{{Testcase_gnome-shell_generic_setup}} | {{Testcase_gnome-shell_generic_setup}} | ||
# Have several extensions installed as in [[QA:Testcase_gnome-shell_extensions_install|previous]] case. | # Have several extensions installed as in [[QA:Testcase_gnome-shell_extensions_install|previous]] case. | ||
|actions= | |actions= | ||
# |results= | # Check that the ''Gnome Shell Integration'' plugin is loaded in the browser of your choice. This can be done by typing ''about:plugins'' in most browsers - Firefox as well as web-kit based ones. | ||
# }} | # Using this browser go to https://extensions.gnome.org/ | ||
# Follow the ''Installed extensions'' menu link to see the list of extensions you currently have installed on your system. | |||
# Try enabling/disabling various extensions for some time. | |||
# Go back to the main page and browse through available extensions | |||
## View several detail pages of extensions that had installed before as well as the others. | |||
## Try to disable previously installed (not using web interface) extension. | |||
# Choose a number of new extensions and install/enable them using the switch button and by accepting in the pop-up dialog. | |||
# Disable some out of these newly installed extensions. | |||
|results= | |||
# Coming to the ''extensions.gnome.org'' website, it should load and no red warning box should appear. | |||
# With step three, you should see all your currently installed extensions and whether they are loaded. This list should be coherent with the content of ''gnome-tweak-tool'' ''Extensions'' tab. | |||
# Just as when doing so with ''gnome-tweak-tool'', as you keep enabling and disabling extensions they should load / unload accordingly. If the extension switch doesn't come to ''on'' when you try, this may be because of incompatible/faulty extension as well as the management system. If you are unsure of what is the case, please, check up with us on IRC before filling a bug. However even if particular extension is faulty, gnome-shell should in no case crash. Please note that some extensions won't visibly alter gnome-shell when you enable them unless some conditions have been met (Media player indicator needs some media playing etc.). | |||
# With step five, verify that button (on/off) on individual extension's pages represents their current state, both for extensions you've installed/enabled online and those you've installed and enabled before. | |||
# All newly installed extensions should install and get enabled properly. Please keep the limitations of results point two here as well. | |||
# All extensions disabled on their individual pages should unload, yet not uninstall. | |||
}} | |||
[[Category:Package_gnome-shell_test_cases]] | [[Category:Package_gnome-shell_test_cases]] |
Revision as of 09:45, 15 March 2012
Description
This test case aims at extensions.gnome.org extension management made available in your favourite browser by Gnome Shell Integration plugin.
Setup
- Boot into a GNOME session with GNOME Shell
- Have several extensions installed as in previous case.
How to test
- Check that the Gnome Shell Integration plugin is loaded in the browser of your choice. This can be done by typing about:plugins in most browsers - Firefox as well as web-kit based ones.
- Using this browser go to https://extensions.gnome.org/
- Follow the Installed extensions menu link to see the list of extensions you currently have installed on your system.
- Try enabling/disabling various extensions for some time.
- Go back to the main page and browse through available extensions
- View several detail pages of extensions that had installed before as well as the others.
- Try to disable previously installed (not using web interface) extension.
- Choose a number of new extensions and install/enable them using the switch button and by accepting in the pop-up dialog.
- Disable some out of these newly installed extensions.
Expected Results
- Coming to the extensions.gnome.org website, it should load and no red warning box should appear.
- With step three, you should see all your currently installed extensions and whether they are loaded. This list should be coherent with the content of gnome-tweak-tool Extensions tab.
- Just as when doing so with gnome-tweak-tool, as you keep enabling and disabling extensions they should load / unload accordingly. If the extension switch doesn't come to on when you try, this may be because of incompatible/faulty extension as well as the management system. If you are unsure of what is the case, please, check up with us on IRC before filling a bug. However even if particular extension is faulty, gnome-shell should in no case crash. Please note that some extensions won't visibly alter gnome-shell when you enable them unless some conditions have been met (Media player indicator needs some media playing etc.).
- With step five, verify that button (on/off) on individual extension's pages represents their current state, both for extensions you've installed/enabled online and those you've installed and enabled before.
- All newly installed extensions should install and get enabled properly. Please keep the limitations of results point two here as well.
- All extensions disabled on their individual pages should unload, yet not uninstall.