New Page: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= ''' |
= ''' Keyboard ''' = |
||
=== How did you do the testing? === |
=== How did you do the testing? === |
||
*First of all made a proper plan for testing with the good understanding about the scope. |
|||
*If the Laptop is XO1.0 download the developer key. If it is XO1.5 no need a developer key |
|||
*According to the plan I divided the testing areas into sub parts like alphanumeric, numeric, letters, special characters, etc |
|||
*Using the terminal activity get a copy of the developer key and save in centralized place. |
|||
*Then define the inputs and according to those input defined the expected results. |
|||
*Disable the security |
|||
*I use two testing interfaces those are write activity and OK prompt. |
|||
*Download the latest releases of the OS and save it in the USB memory stick |
|||
*For the testing of the alphanumeric, numeric, letters are used the write activity. |
|||
*If the Laptop is XO1.0 download the firmware as well and saves in the USB memory stick. If it is a XO1.5 no need to manually update the firmware; it will automatically update while updating the OS. But the user wants to update it manually, user can do. |
|||
*Used the OK prompt for the other buttons testing. |
|||
*Some of the laptops are installed the OS without disabling the security. Then got stuck (This problem has solved using different way and it has mentioned in the guide document with full details) |
|||
*In OK prompt, typed the “test keyboard” command to go to the inbuilt keyboard testing function. |
|||
== What kind of problems that you had to face? == |
== What kind of problems that you had to face? == |
||
In keyboard testing I didn’t have any problem and testing is gone smoothly. |
|||
When installing the OS according to the steps that mentioned in the official website, it was not worked. So we had to find proper ways to do the installations |
|||
== Defects you have found: == |
== Defects you have found: == |
||
Latest revision as of 05:43, 4 June 2010
Keyboard
How did you do the testing?
- First of all made a proper plan for testing with the good understanding about the scope.
- According to the plan I divided the testing areas into sub parts like alphanumeric, numeric, letters, special characters, etc
- Then define the inputs and according to those input defined the expected results.
- I use two testing interfaces those are write activity and OK prompt.
- For the testing of the alphanumeric, numeric, letters are used the write activity.
- Used the OK prompt for the other buttons testing.
- In OK prompt, typed the “test keyboard” command to go to the inbuilt keyboard testing function.
What kind of problems that you had to face?
In keyboard testing I didn’t have any problem and testing is gone smoothly.
Defects you have found:
No defects found