From Fedora Project Wiki

No edit summary
Line 20: Line 20:


=== How to test? ===
=== How to test? ===
The idea is to test common actions in desktop applications using your native language.
The idea is to test common usage in your desktop applications in your native language, and identify any problems or weaknesses.
It is better to start testing with a fresh account or Live instance (without persistence).


The main focus areas are:
The main focus areas are:
Line 27: Line 26:
* input using ibus
* input using ibus
* printing
* printing
It is recommended to test from fresh account or Live instance (without persistence).


=== Test Cases ===
=== Test Cases ===

Revision as of 07:02, 27 October 2009

DATE TIME WHERE
2009-10-29 Daytime US EDT and Asia-Pacific Daytime #fedora-test-day (webirc)

What to test?

Today's installment of Fedora Test Day will focus on i18n

Who's available

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

Prerequisite for Test Day

  • Usb key, or
  • Rawhide Fully updated

How to test?

The idea is to test common usage in your desktop applications in your native language, and identify any problems or weaknesses.

The main focus areas are:

  • display of text in browser, openoffice, etc
  • input using ibus
  • printing

It is recommended to test from fresh account or Live instance (without persistence).

Test Cases

Test Results

Problems identified

Using your own test scenarios, or any of the test cases listed above, please outline problems/failures you encounter using the table below.

Tester Language Desktop Application Problems Bug references
Tester Language Desktop Application Problems Bug reference(s)

Just worked

Provide a list of tests or scenarios that behaved flawlessly.

Tester Language Desktop Applications tested
Tester Language Desktop Applications tested