New Page: Difference between revisions
Jump to navigation
Jump to search
(Created page with '= '''Calculator''' = == Description: == This Activity is available in both XO1 and XO 1.5. The Calculator Activity can simply use to solve simple functions and also for Plot gr…') |
No edit summary |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= ''' |
= ''' Keyboard ''' = |
||
== Description: == |
|||
This Activity is available in both XO1 and XO 1.5. The Calculator Activity can simply use to solve simple functions and also for Plot graphs. This is a very useful activity for a child. This has many scientific functionalities such as Algebra, Trigonometry, Boolean and Miscellaneous where a grownup child could use in studies. |
|||
=== 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. |
||
*According to the plan I divided the testing areas into sub parts like alphanumeric, numeric, letters, special characters, etc |
|||
* Then I went through the OLPC WIKI links to get an idea on how it works. |
|||
*Then define the inputs and according to those input defined the expected results. |
|||
* I performed Smoke Testing to confirm my understanding on the activity. |
|||
*I use two testing interfaces those are write activity and OK prompt. |
|||
* Then started to design the tests using the Decision Tree Diagrams. |
|||
*For the testing of the alphanumeric, numeric, letters are used the write activity. |
|||
* According to Decision Tree Diagrams, I wrote the test cases using the Test Case template. |
|||
*Used the OK prompt for the other buttons testing. |
|||
* After completing the Peer and Lead Reviews, started the Testing and recorded the Test Results. |
|||
*In OK prompt, typed the “test keyboard” command to go to the inbuilt keyboard testing function. |
|||
* If a defect found, I went through the history of OLPC and Sugar lab to check whether the defects has already risen or not. |
|||
* If not, I raised the defect (ticket). |
|||
== 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. |
|||
* Downloading issues. |
|||
* Previously raised defects were not fixed in newly released builds. |
|||
* No proper understanding about some functionalities functionality, due to lack of information available. |
|||
* As a solution, went through the WIKI, Google mailing list to clarify those functionalities as possible. |
|||
== Defects you have found: == |
== Defects you have found: == |
||
No defects found |
|||
* #1865 : http://bugs.sugarlabs.org/ticket/1865 |
|||
* #1870 : http://bugs.sugarlabs.org/ticket/1870 |
|||
* #1903 : http://bugs.sugarlabs.org/ticket/1903 |
|||
* #1909 : http://bugs.sugarlabs.org/ticket/1909 |
|||
* #1910 : http://bugs.sugarlabs.org/ticket/1910 |
|||
* #1937 : http://bugs.sugarlabs.org/ticket/1937 |
|||
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