Testcase ibus input

Description

This test case tests input works correctly for your ibus input method.

How to test

Requisition

• Desktop Environment to test: GNOME, KDE4
• Focus policy to test: focus-on-click, focus-follow mouse.
• Application to test:
  • Console: xterm, gnome-terminal, konsole.
  • Editors: gedit, kate, gvim, emacs
  • OpenOffice: writer, calc, impress
  • Internet: firefox, thunderbird, pidgin
  • Others: evolution, eclipse

Prepare at least 3 test sentences, preferably mixed with English words and punctuation marks.

For each desktop environments and focus policies:

1. Basic test: Input test sentences to each application.
2. Candidate selection test +: Modify a few characters in test sentences by invoking the candidate selection dialog.
3. Incomplete character handling test *: Just type a part of character, then perform following sub-tests:
   1. switch on/off:
      1. switch on IM, type an incomplete words, then switch off IM.
      2. Type a few English keys.
      3. switch on IM, then type an different characters
   2. 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.
4. Pre-edit buffer test $:Type a few complete characters and an incomplete character in pre-edit buffer. Then perform following sub-tests:
   1. switch on/off: Similar to the counterpart in Incomplete character test.
   2. focus in/out: Similar to the counterpart in Incomplete character test.

• +: Required if IM offers the choice among matching candidates.
• *: 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.
• $: 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.

Expected Results

1. Basic test: Committed string should be exactly same as test sentences.
2. Candidate selection test: Committed string should reflect the modified characters.
3. Incomplete character handling test: Incomplete character should not appear in committed string, while other input should be shown as normal.
4. Pre-edit buffer test: Incomplete characters should not appear, while complete characters should be in the committed string.