New Page: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
= ''' Keyboard ''' =
[[econ101newpage|New Page]]
= ''' Audio,Screen and Charging''' =




=== 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.
*I used a self-test method in OK prompt to test audio & screen. Also I tried it in external microphone and headphones.
*According to the plan I divided the testing areas into sub parts like alphanumeric, numeric, letters, special characters, etc
*I tested the left, right speakers & microphone using browser & TamTammini activities. Also tested the external audio output & Line in function.
*Then define the inputs and according to those input defined the expected results.
*How long it took to charge the battery full. (Full Charge).
*I use two testing interfaces those are write activity and OK prompt.
*Tested the OLPC functions while the battery was dead and the power charger is plugged.
*For the testing of the alphanumeric, numeric, letters are used the write activity.
*Screen frame area tested using frame key function.
*Used the OK prompt for the other buttons testing.
*Backlight function also tested.
*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.

*Issues in updating Activities
*Issues in Activity version
*Functionality of playing audio when power management is on, was not understood properly.
*Screen rotation function in XO 1.5 had issues
*Camera in XO 1.5 had issues.



== Defects you have found: ==
== Defects you have found: ==
No defects found


* #1901 : http://bugs.sugarlabs.org/ticket/1901
* #1906 : http://bugs.sugarlabs.org/ticket/1906
* #1945 : http://bugs.sugarlabs.org/ticket/1945

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