New Page: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
=== 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. |
*First of all made a proper plan for testing with the good understanding about the scope. |
||
*Identified what are the indicators which XO is having and made a separate testing plan for each indicator. |
|||
*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. |
*Then define the inputs and according to those input defined the expected results. |
||
*I |
*I used many activities for the testing such as record activity for the camera indicator testing. |
||
*I have spent more time for testing those indicators because of hardware side testing. For an instance battery indicator testing, I had to have waited long time for battery dead mode, low mode. |
|||
*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? == |
== What kind of problems that you had to face? == |
||
For the Wi-Fi indicator testing and storage access indicator (when the pen drive plugged) we had to obey the virtusa policies. So it was a hard time. |
|||
In keyboard testing I didn’t have any problem and testing is gone smoothly. |
|||
Revision as of 05:39, 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.
- Identified what are the indicators which XO is having and made a separate testing plan for each indicator.
- Then define the inputs and according to those input defined the expected results.
- I used many activities for the testing such as record activity for the camera indicator testing.
- I have spent more time for testing those indicators because of hardware side testing. For an instance battery indicator testing, I had to have waited long time for battery dead mode, low mode.
What kind of problems that you had to face?
For the Wi-Fi indicator testing and storage access indicator (when the pen drive plugged) we had to obey the virtusa policies. So it was a hard time.
Defects you have found:
No defects found