New Page: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= ''' |
= ''' Indicators ''' = |
||
=== 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 |
|||
*Identified what are the indicators which XO is having and made a separate testing plan for each indicator. |
|||
*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 used many activities for the testing such as record activity for the camera indicator testing. |
|||
*Download the latest releases of the OS and save it in the USB memory stick |
|||
*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. |
|||
*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. |
|||
*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) |
|||
== 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. |
|||
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 |
|||
Revision as of 05:34, 4 June 2010
Indicators
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