From Fedora Project Wiki

No edit summary
No edit summary
(23 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{admon/warning|Making changes to this page|Please make changes to this wiki page, '''not''' the ''Template:Test_Case'' page.  This can be accomplished by clicking the ''edit'' link at the top of this page.  Any changes to ''Template:Test_Case'' show up in ''every'' test case wiki page that uses that template.}}
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests input works correctly for your ibus input method.
|description=This test-case is to check that input works correctly for your ibus input-method.
|setup=
Follow up to the steps in [[QA:Testcase i18n input method setup]] to configure the input method on the desktop.
|actions=
|actions=
== Requisition ==
You may want to prepare some test sentences and/or phrases to input preferably mixed with some ASCII (eg English) text including punctuation.
Desktop Environment to test: GNOME, KDE4
# General test: input test sentences into various applications you use often.  Test both with the input-method on and off and make sure you can input all the characters you commonly use on your keyboard.
Focus policy to test: focus-on-click, focus-follow mouse.
# Additional tests for '''Chinese, Japanese and Korean''' users (who are testing '''hanja''' input):
Application to test:
## Modify a few characters in your test sentences invoking candidate selection.
  Console: xterm, gnome-terminal, konsole.
## Incomplete character handling tests:
  Editors: gedit, kate, gvim, emacs
### switch off/on:
  OpenOffice: writer, calc, impress
#### switch on IM, type an incomplete word and then switch off IM.
  Internet: firefox, thunderbird, pidgin
#### type a few English keys.
  Others: evolution, eclipse
#### switch on IM again, then input a different character
 
### focus out/in: Similar to the previous on/off subtest, but switch focus to another window with the mouse to focus out, type some text, then focus back on the application with the mouse.
Prepare at least 3 test sentences, preferably mixed with English words and punctuation marks.
## Pre-edit buffer test: type a few complete characters and an incomplete character in pre-edit buffer. Then perform the following sub-tests:
### Switch off/on: with some pre-edit text try turning off the input-method, input some ASCII text, turn on the input-method again and continue to input with the input method.
### Focus out/in: with some pre-edit test switch focus to another window with the mouse, input some text there, return to your application and continue your input
|results=
# General test: Committed string should be expected text from your test sentences.
# Additional CJK tests:
## Candidate selection test: Committed string should reflect the modified characters: the expected behaviour may vary somewhat depending on the language being tested.
## Incomplete character handling test: Incomplete characters should not appear in the committed string, while other input should be shown as normal.
## Pre-edit buffer test: Incomplete characters should not appear, while complete characters should be in the committed string (it is OK if the contents of the Pre-edit buffer are lost on focus out/in or turning the input method off and on again).
}}


For each desktop environments and focus policies:
= Other features =
# Basic test: Input test sentences to each application.
* [[QA:Testcase_ibus_start|IBus Start]]
# Candidate selection test [[#Remark1|+]]: Modify a few characters in test sentences by invoking the candidate selection dialog.
* [[QA:Testcase_ibus_gnome_shell|GNOME-Shell]]
# Incomplete character handling test [[#Remark2|++]]: Just type a part of character, then perform following sub-tests:
# switch on/off:
  # switch on IM, type an incomplete words, then switch off IM.
  # Type a few English keys.
  # switch on IM, then type an different characters
# focus in/out: Similar to on/off sub-test, but click on other window to focus out, type a few English word, then focus in by click back on the application.
# Pre-edit buffer test [[#Remark3|+++]]:
  Similar to incomplete character test. Since pre-edit buffer may contain both incomplete and completed characters, 
 
<div id="Remark1">+</div>
[[Anchor Remark1]]
+: Required if IM offers the choice among matching candidates.


[[Anchor Remark2]]
[[Category:Package_ibus_test_cases]]
++: Required if IM needs more than one key to form a complete-character. For example, Chinese IMs require more than one key to form a Chinese character.
[[Category:I18n_Desktop]]
 
[[Anchor Remark3]]
+++: Required if IM use pre-edit buffer to store phrases. ibus-pinyin and ibus-chewing are examples of IM that need to perform this test.
 
|results=
# expected results
}}
[[Category:IBus_Test_Cases]]

Revision as of 07:38, 20 March 2015

Description

This test-case is to check that input works correctly for your ibus input-method.

Setup

Follow up to the steps in QA:Testcase i18n input method setup to configure the input method on the desktop.

How to test

You may want to prepare some test sentences and/or phrases to input preferably mixed with some ASCII (eg English) text including punctuation.

  1. General test: input test sentences into various applications you use often. Test both with the input-method on and off and make sure you can input all the characters you commonly use on your keyboard.
  2. Additional tests for Chinese, Japanese and Korean users (who are testing hanja input):
    1. Modify a few characters in your test sentences invoking candidate selection.
    2. Incomplete character handling tests:
      1. switch off/on:
        1. switch on IM, type an incomplete word and then switch off IM.
        2. type a few English keys.
        3. switch on IM again, then input a different character
      2. focus out/in: Similar to the previous on/off subtest, but switch focus to another window with the mouse to focus out, type some text, then focus back on the application with the mouse.
    3. Pre-edit buffer test: type a few complete characters and an incomplete character in pre-edit buffer. Then perform the following sub-tests:
      1. Switch off/on: with some pre-edit text try turning off the input-method, input some ASCII text, turn on the input-method again and continue to input with the input method.
      2. Focus out/in: with some pre-edit test switch focus to another window with the mouse, input some text there, return to your application and continue your input

Expected Results

  1. General test: Committed string should be expected text from your test sentences.
  2. Additional CJK tests:
    1. Candidate selection test: Committed string should reflect the modified characters: the expected behaviour may vary somewhat depending on the language being tested.
    2. Incomplete character handling test: Incomplete characters should not appear in the committed string, while other input should be shown as normal.
    3. Pre-edit buffer test: Incomplete characters should not appear, while complete characters should be in the committed string (it is OK if the contents of the Pre-edit buffer are lost on focus out/in or turning the input method off and on again).



Other features