From Fedora Project Wiki

(Test Results)
(Prerequisite for Test Day)
Line 26: Line 26:
 
* One or more keyboards with different layouts.
 
* One or more keyboards with different layouts.
 
* Bare metal or virtual machine.
 
* Bare metal or virtual machine.
* Usb key, a virtualized guest or a burned CD/DVD with the [http://fedoraproject.org/get-prerelease test image(TBD)]
+
* Usb key, a virtualized guest or a burned CD/DVD with the [https://getfedora.org/workstation/prerelease/ F22 Alpha image] or the [http://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC2/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-22_Beta-TC2.iso testing compose image] if you like.
 +
** that may be not the latest. please check the [http://dl.fedoraproject.org/pub/alt/stage/ place] to see the latest.
  
 
== How to test? ==
 
== How to test? ==

Revision as of 06:13, 18 March 2015

Fedora Test Days
Echo-testing-48px.png
I18N

Date 2015-03-19
Time all day

Website [Fedora Calendar]
IRC #fedora-test-day (webirc)

Mailing list
MailSubscribeArchives


Note.png
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 Internationalization a.k.a. i18n around Desktops including their applications. this aims to ensure if i18n support works enough on them.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

  • One or more keyboards with different layouts.
  • Bare metal or virtual machine.
  • Usb key, a virtualized guest or a burned CD/DVD with the F22 Alpha image or the testing compose image if you like.
    • that may be not the latest. please check the place to see the latest.

How to test?

(TBD)

High level details on how a contributor can get involved. This can include (but not limited to):

  • Areas to target with exploratory testing
  • A list of pre-defined test cases to execute
  • How to report back results

Here's another common chunk (again, replace XX as above):

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

Test Results

Please enter results for planned testing on the result page.

If you have problems with any of the tests, report a bug to Bugzilla with i18n keyword. For instance file a bug report against the component firefox if you have problems testing the Firefox Web Browser. adding i18n keyword to Keywords field in bugzilla is important part in order to keep it on track. 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 separate pages by testing categories below.