Fedora Test Days | |
---|---|
![]() | |
L10n Desktop | |
Date | 2011-08-30 |
Time | all day |
Website | QA/Fedora_16_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's installment of Fedora Test Day will focus on translations availability and accuracy in desktop applications
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development -
- Quality Assurance - IgorSoares (igorps), Rhe (rhe), Aalam (alam)
Prerequisite for Test Day
- Bare metal or virtual machine.
- Usb key, a virtualized guest or a burned CD/DVD with the test image
How to test?
Prepare Your System
- Tests requiring physical media (e.g. DVD or CD images)
- You may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. The specific live image for L10N tests can be found here.
- Unless otherwise noted, you may use nightly Fedora 16 branch install images. Review for information on downloading and installing Branched.
- If you are using a Alpha or pre-Alpha installation please keep in mind to update your system before running the tests.
Nice to test
Bugs you might hit or additional situations that are nice to test:
- (as_IN)(gtk)(Translation) - Translation Error with "????" appearing
- (te_IN) Disk format message is out of screen during installation
- No translation on Login-Page of the reboot-menu
- (all languages) yum untranslated words
- Semi-translated messages (translated strings missing)
Test Results
Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at Bugzilla against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. 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.
Translation teams are free to prioritize packages they find more important to test. Please use the following format when posting results to this page:
Example | Explanation | Wiki text |
---|---|---|
Untested | {{result|none}}
| |
![]() |
Indicates a test that has passed | {{result|pass|lang_CODE}}
|
![]() |
Indicates a test currently assigned and inprogress | {{result|inprogress|lang_CODE}}
|
![]() |
Indicates a test that needs further review
|
{{result|warn|lang_CODE}}<ref>some comments here.</ref>
|
![]() |
Indicates a failed test ... see Comment/Bug(s) for details | {{result|fail|lang_CODE}}
|
Test Matrix
Package | Steps | Result [language code] | Bug | Comment |
---|---|---|---|---|
|
Issue command example |
![]() |
RHBZ #678583 | |
|
Issue command abrt-gui |
|||
|
Issue command liveinst |
![]() |
RHBZ #734278 RHBZ #734279 RHBZ #734280 | Perform this first to install onto hard drive. Also test the keyboard layout behavior according to [1] |
|
Issue command audit-viewer |
|||
|
Issue command authconfig |
|||
|
Issue command chkconfig |
|||
|
Check .PO file | |||
|
n/a (this can be checked through anaconda test using the install media) | |||
|
Go to System -> Settings -> Appearance | |||
|
This can be checked by pressing Esc during system boot-up |
|||
|
Issue command preupgrade and preupgrade-cli |
|||
|
Issue command desktop-effects |
|||
|
As root ("su -" or "sudo"), issue command firstboot |
|||
|
Check .PO file | |||
|
Issue command im-chooser |
|||
|
Issue command iok |
|||
|
Issue command kexec -h |
|||
|
Check .PO file | |||
|
Issue command liveusb-creator |
|||
|
Issue command locate -h |
|||
|
Go to Application -> Sound & Video -> Output Generation | |||
|
Check .PO file | |||
|
Issue command passwd -? |
|||
|
Issue command system-config-selinux and selinux-polgengui |
|||
|
Check .PO file | |||
|
Check .PO file | |||
|
Check desktop menu | |||
|
Issue command sealert -b |
|||
|
Issue command setup |
|||
|
Issue command smoltGui and as root, issue command firstboot and check the section of 'Hardware Profile' |
|||
|
Check .PO file | |||
|
Become root using either su - or sudo ), issue command sosreport |
|||
|
Issue command switchdesk |
|||
|
Issue command system-config-audit |
|||
|
Issue command system-config-bind |
|||
|
Issue command system-config-boot |
|||
|
Issue command system-config-date |
|||
|
Issue command system-config-firewall |
|||
|
Issue command system-config-httpd |
|||
|
Issue command system-config-kdump |
|||
|
Issue command system-config-keyboard |
|||
|
Issue command system-config-kickstart |
|||
|
Issue command system-config-language |
|||
|
Issue command system-config-lvm |
|||
|
Issue command system-config-netboot |
|||
|
Issue command system-config-network |
|||
|
Issue command system-config-nfs |
|||
|
Issue command system-config-printer |
|||
|
Issue command system-config-rootpassword |
|||
|
Issue command system-config-samba |
|||
|
Issue command system-config-services |
|||
|
Issue command system-config-users |
|||
|
Issue command system-switch-java |
|||
|
Become root using either su - or sudo , issue command system-switch-mail |
|||
|
Become root using either (su - or sudo ), issue command usermode |