Re: Feedback on i18n test cases

[Akira TAGOH]

Thank you for the feedback.

----- 元のメッセージ -----
| Few suggestions are listed down, which were found during the dry run of
| the i18n test cases:
| 
| 1. Each time after you do the testing, need to to come back to the test
| day page and then scroll down to go the Result section
| Suggestion: Provide the link for result page on each test case page and
| also link each result page to the test case page.
| ie. In the "Input (Overall) section, we have two test cases: QA:Testcase
| i18n ibus input and QA:Gnome Input Method Integration IBus.
| (i) Provide the link for the result page of Input (Overall) in these two
| test cases' page so that from tester perspective navigating between test
| case and result pages will be easier.

test cases are also used for updates in bodhi. so I think adding a link to the result page
is not a good idea, which is test day specific.

| (ii) Also can provide these two test cases' pages link in the
| Input(Overall) result page

Sure. that sounds reasonable.

| 
| 2. QA:Testcase ibus input: Found the instructions bit confusing and
| difficult to understand

Which one particularly? can you mention more details?

| 
| 3. Input (language-specific): Didnt find the command to run the typing
| booster application.

the command?

--
Akira TAGOH

Feedback on i18n test cases

[Sweta Kothari]

Thanks Tagoh & Ani for your valuable feedback.

In addition to that, I had some more points:

Input (overall):-

1] I agree with Ani on the following point: The link to view/update the
test results should be moved on the page that has the test case steps &
expected results. This way it would become easy for the Tester to
navigate the pages.

2] Gnome Input Method Integration IBus : This test case is more
applicable for f18 but not applicable for f19, because There is no
restart button on ibus icon as UI changed totally in f19 and For change
the layout, Hot key has been changed from "ctrl+space" to
"Super+space".

Input (language-specific):-

1] On test results page, There should be a cloumn to define the test
case If there are multiple test cases so tester can record results
appropriately

2] inscript2 keymap : Please mention the language for which the key
combination need to be tested.i have tested for Altgr+f, Altgr+r, But
they are not working in my language.

3] Intelligent_Pinyin:There is no preference dialog to change the
layout, For F19 Ui is changed totally, This test case instuction totally
says for f18 perpsepctive.

Rendering:-

On test results page, There should be a cloumn to define the test case
If there are multiple test cases so tester can record results appropriately


Thanks,
Sweta


On 04/30/2013 02:41 PM, Akira TAGOH wrote:
>  Thank you for the feedback.
>  
>  ----- 元のメッセージ -----
>  | Few suggestions are listed down, which were found during the dry run of
>  | the i18n test cases:
>  | 
>  | 1. Each time after you do the testing, need to to come back to the test
>  | day page and then scroll down to go the Result section
>  | Suggestion: Provide the link for result page on each test case page and
>  | also link each result page to the test case page.
>  | ie. In the "Input (Overall) section, we have two test cases: QA:Testcase
>  | i18n ibus input and QA:Gnome Input Method Integration IBus.
>  | (i) Provide the link for the result page of Input (Overall) in these two
>  | test cases' page so that from tester perspective navigating between test
>  | case and result pages will be easier.
>  
>  test cases are also used for updates in bodhi. so I think adding a link to the result
> page is not a good idea, which is test day specific.
>  
>  | (ii) Also can provide these two test cases' pages link in the
>  | Input(Overall) result page
>  
>  Sure. that sounds reasonable.
>  
>  | 
>  | 2. QA:Testcase ibus input: Found the instructions bit confusing and
>  | difficult to understand
>  
>  Which one particularly? can you mention more details?
>  
>  | 
>  | 3. Input (language-specific): Didnt find the command to run the typing
>  | booster application.
>  
>  the command?
>  
>  --
>  Akira TAGOH
>  --
>  i18n mailing list
>  i18n(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/i18n

Feedback on i18n test cases

[Akira TAGOH]

Thanks for the comment.

----- 元のメッセージ -----
| Input (language-specific):-
| 
| 1] On test results page, There should be a cloumn to define the test
| case If there are multiple test cases so tester can record results
| appropriately

That is an intentional change to see the overall results if it is good or not. please add
a comment what test cases particularly failed.

--
Akira TAGOH

Feedback on i18n test cases

[Akira TAGOH]

----- 元のメッセージ -----
| 3] Intelligent_Pinyin:There is no preference dialog to change the
| layout, For F19 Ui is changed totally, This test case instuction totally
| says for f18 perpsepctive.

Well, basically there are no changes how to access the preferences for engines. it's
the same to f18 that you can access from gnome-control-center only - select the input
source what you want to see the preference. click the gear icon at the bottom of the input
sources section.

--
Akira TAGOH

Feedback on i18n test cases

[Parag Nemade]

Hi,
On 04/30/2013 11:10 PM, Sweta Kothari wrote:
>  Input (language-specific):-
>
>  2] inscript2 keymap : Please mention the language for which the key
>  combination need to be tested.i have tested for Altgr+f, Altgr+r, But
>  they are not working in my language. 
For the Inscript2 test,
1) Test that you can set R_ALT key as AltGr as per given on testcase page
2) Use the Enhanced Inscript draft standard pdf given in the Results 
section on the testcase page and verify all the keymappings are 
according to the standard defined for your Indic language.

Regards,
Parag.

Feedback on i18n test cases

[Akira TAGOH]

The links of test cases has been moved to each result pages now.

---
Akira TAGOH

----- 元のメッセージ -----
| Thank you for the feedback.
| 
| ----- 元のメッセージ -----
| | Few suggestions are listed down, which were found during the dry run of
| | the i18n test cases:
| | 
| | 1. Each time after you do the testing, need to to come back to the test
| | day page and then scroll down to go the Result section
| | Suggestion: Provide the link for result page on each test case page and
| | also link each result page to the test case page.
| | ie. In the "Input (Overall) section, we have two test cases: QA:Testcase
| | i18n ibus input and QA:Gnome Input Method Integration IBus.
| | (i) Provide the link for the result page of Input (Overall) in these two
| | test cases' page so that from tester perspective navigating between test
| | case and result pages will be easier.
| 
| test cases are also used for updates in bodhi. so I think adding a link to
| the result page is not a good idea, which is test day specific.
| 
| | (ii) Also can provide these two test cases' pages link in the
| | Input(Overall) result page
| 
| Sure. that sounds reasonable.
| 
| | 
| | 2. QA:Testcase ibus input: Found the instructions bit confusing and
| | difficult to understand
| 
| Which one particularly? can you mention more details?
| 
| | 
| | 3. Input (language-specific): Didnt find the command to run the typing
| | booster application.
| 
| the command?
| 
| --
| Akira TAGOH
| _______________________________________________
| fltg mailing list
| fltg(a)lists.fedoraproject.org
| https://admin.fedoraproject.org/mailman/listinfo/fltg
|