1. A mobile device for connecting with an external input device, the mobile device comprising:
a first connector for receiving an input signal generated by the external input device through a docking station, the first connector being detachably connected with the docking station; and
a first controller for receiving the input signal from the first connector and executing a pre-stored function corresponding to the received input signal.
2. The mobile device of claim 1, wherein the external input device comprises at least one of a mouse device and a keyboard.
3. The mobile device of claim 1, wherein the docking station comprises:
a second connector which is connected with the first connector of the mobile device;
a third connector which is connected with the external input device; and
a second controller for receiving an input signal through the third connector from the external input device and transmitting the received input signal to the mobile device through the second connector.
4. The mobile device of claim 1, wherein the pre-stored function comprises at least one function performed in the mobile device.
5. The mobile device of claim 4, wherein the external input device is a mouse device including at least one of a first button and a second button, and
an input signal for performing a home button function of the mobile device is generated when the first button is pressed, and
an input signal for performing a back button function of the mobile device is generated when the second button is pressed.
6. The mobile device of claim 5, wherein the first button of the mouse device is a wheel button, and the second button of the mouse device is a side button.
7. The mobile device of claim 1, wherein the first controller moves a cursor displayed on a screen of the mobile device corresponding to the input signal, and changes the pre-stored function in accordance with an area of the screen where the cursor is located.
8. The mobile device of claim 1, wherein the first controller displays a menu window including a menu item corresponding to the pre-stored function on a screen of the mobile device when receiving a pre-stored input signal, and executes the pre-stored function corresponding to the menu item when detecting a selection of the menu item.
9. The mobile device of claim 1, wherein the first controller displays each icon corresponding to at least one function performed in the mobile device on a screen of the mobile device when the first connector is connected with the docking station, and executes the at least one function corresponding to the each icon when the each icon is selected.
10. The mobile device of claim 1, wherein the first controller moves a cursor displayed on a screen of the mobile device corresponding to the input signal,
displays an icon indicating a button on the screen when the cursor is located near the button included in the mobile device, and
executes a function which is equivalent to the button when the icon is selected.
11. The mobile device of claim 1, wherein the input signal allows a cursor displayed on a screen of the mobile device to touch an edge of the screen.
12. A method for controlling a mobile device which is connected with an external input device, the method comprising:
receiving an input signal generated by the external input device through a docking station, at a first connector of the mobile device; and
executing a pre-stored function corresponding to the received input signal.
13. The method of claim 12, wherein the external input device comprises at least one of a mouse device and a keyboard.
14. The method of claim 12, wherein the docking station receives an input signal through a third connector from the external input device and transmits the received input signal to the mobile device through a second connector which is connected with the first connector of the mobile device.
15. The method of claim 12, wherein the pre-stored function comprises at least one function performed in the mobile device.
16. The method of claim 15, wherein the external input device is a mouse device including at least one of a first button and a second button, and
an input signal for performing a home button function of the mobile device is generated when the first button is pressed, and
an input signal for performing a back button function of the mobile device is generated when the second button is pressed.
17. The method of claim 16, wherein the first button of the mouse device is a wheel button, and the second button of the mouse device is a side button.
18. The method of claim 12, further comprising moving a cursor displayed on a screen of the mobile device corresponding to the input signal, and the pre-stored function is changed in accordance with an area of the screen where the cursor is located.
19. The method of claim 12, further comprising:
displaying a menu window including a menu item corresponding to the pre-stored function on a screen of the mobile device when a pre-stored input signal is received; and
executing the pre-stored function corresponding to the menu item when a selection of the menu item is detected.
20. The method of claim 12, further comprising:
detecting a connection between the first connector and the docking station;
displaying each icon corresponding to at least one function performed in the mobile device on a screen of the mobile device when the connection between the first connector and the docking station is detected; and
executing the at least one function corresponding to the each icon when the each icon is selected.
21. The method of claim 12, further comprising:
moving a cursor displayed on a screen of the mobile device corresponding to the input signal;
displaying an icon indicating a button on the screen when the cursor is located near the button included in the mobile device; and
executing a function which is equivalent to the button when the icon is selected.
22. The method of claim 12, wherein the input signal allows a cursor displayed on a screen of the mobile device to touch an edge of the screen.
23. A docking station which is connected with an external device, the docking station comprising:
a first connector for connecting with the external device for receiving an input signal generated by the external device;
a second connector for connecting with a mobile device for transmitting the received input signal to the mobile device; and
a controller for transmitting the received input signal to the mobile device through the first connector and the second connector.
24. The docking station according to claim 23, wherein the mobile device comprises a third connector which is connected to the second connector of the docking station.
25. The docking station according to claim 23, wherein the mobile device is attached to the second connector of the docking station through a third connector, or is detached from the docking station.
26. The docking station according to claim 23, wherein a pre-stored function is executed in the mobile device, corresponding to the received input signal.
The claims below are in addition to those above.
All refrences to claims which appear below refer to the numbering after this setence.
1. A method comprising:
providing an input and an expected test output for a unit test;
executing the unit test using a module under test and the input, thereby generating an actual test output; and
serializing the expected test output and the actual test output into an XML format; and
comparing the XML expected test output and the XML actual test output.
2. The method of claim 1, further comprising:
calculating a checksum of the serialized actual test output and the serialized expected test output; and
comparing the checksum of the actual test output and the checksum of the expected test output.
3. The method of claim 1, further comprising comparing the XML actual test output and the XML expected test output when the checksum of the actual test output and the checksum of the expected test output are not equal.
4. The method of claim 3, wherein the comparing of the XML of the actual test output and the XML of the expected test output comprises:
submitting the XML actual test output to an XML parser;
submitting the XML expected test output to the XML parser;
examining the outputs of the XML parser to determine if the XML of the actual test output and the XML of the expected test output are equal; and
identifying any differences between the XML of the actual test output and the XML of the expected test output.
5. The method of claim 4, wherein the XML parser generates a string from the XML file containing the actual test output and a string from the XML file containing the expected test output, and further comprising comparing the strings to determine if the actual test output is equal to the expected test output.
6. The method of claim 3, wherein the comparing of the XML of the actual test output and the XML of the expected test output comprises:
submitting the XML of the actual test output and the XML of the expected test output to an XML change detection algorithm;
examining the output of the XML change detection algorithm to determine if the XML of the actual test output and the XML of the expected output are equal; and
identifying any differences between the XML of the actual test output and the XML of the expected test output.
7. The method of claim 1, wherein the input for the unit test is captured from a production system that includes a production version of the module under test in the unit test.
8. The method of claim 1, wherein the input for the unit test is captured from the system upon which the unit test is being performed.
9. The method of claims 7 or 8, wherein the capturing of the input for the unit test includes the use of one or more of a debugger, a call trace with data, a programmable data recorder, and a source code generator.
10. The method of claim 1, further comprising removing an instantiation of the module under test after the calculation of the checksum of the actual test output and the checksum of the expected test output when the checksum of the actual test output and the checksum of the expected test output are equal.
11. A system comprising:
an input and an expected test output for a unit test;
a module for executing the unit test using a module under test and the input, thereby generating an actual test output;
a module for serializing the expected test output and the actual test output into an XML format; and
a module for comparing the XML expected test output and the XML actual test output.
12. The system of claim 11, further comprising:
a module for calculating a checksum of the actual test output and a checksum of the expected test output; and
a module for comparing the checksum of the actual test output and the checksum of the expected test output.
13. The system of claim 11, further comprising a module for comparing the XML of the actual test output and the XML of the expected test output when the checksum of the actual test output and the checksum of the expected test output are not equal.
14. The system of claim 13, wherein the module for comparing the XML of the actual test output and the XML of the expected test output comprises:
a module for submitting the XML of the actual test output to an XML parser;
a module for submitting the XML of the expected test output to the XML parser;
a module for examining the outputs of the XML parser to determine if the XML of the actual test output and the XML of the expected test output are equal; and
a module for identifying any differences between the XML of the actual test output and the XML of the expected test output.
15. The system of claim 13, wherein the module for comparing the XML of the actual test output and the XML of the expected test output comprises:
a module for submitting the XML of the actual test output and the XML of the expected test output to an XML change detection algorithm;
a module for examining the output of the XML change detection algorithm to determine if the XML of the actual test output and the XML of the expected output are equal; and
a module for identifying any differences between the XML of the actual test output and the XML of the expected test output.
16. The system of claim 11, wherein the input for the unit test is captured from a production system that includes a production version of the module under test in the unit test; and further wherein the capturing of the input for the unit test includes the use of one or more of a debugger, a call trace with data, a programmable data recorder, and a source code generator.
17. The system of claim 11, wherein the input for the unit test is captured from the system upon which the unit test is being executed, and further wherein the capturing of the input for the unit test includes the use of one or more of a debugger, a call trace with data, a programmable data recorder, and a source code generator.
18. A machine readable medium including instructions that when executed on a machine execute a process comprising:
receiving an input and an expected test output for a unit test;
executing the unit test using a module under test and the input, thereby generating an actual test output;
serializing the expected test output and the actual test output into an XML format; and
comparing the XML expected test output and the XML actual test output.
19. The machine readable medium of claim 18, further comprising instructions for:
calculating a checksum of the actual test output and a checksum for the expected test output; and
comparing the checksum of the actual test output and the checksum of the expected test output.
20. The machine readable medium of claim 18, further comprising instructions for comparing the XML of the actual test output and the XML of the expected test output when the checksum of the actual test output and the checksum of the expected test output are not equal.
21. The machine readable medium of claim 20, wherein the instructions for comparing the XML of the actual test output and the XML of the expected test output comprise:
submitting the XML of the actual test output to an XML parser;
submitting the XML of the expected test output to the XML parser;
examining the outputs of the XML parser to determine if the XML of the actual test output and the XML of the expected test output are equal; and
identifying any differences between the XML of the actual test output and the XML of the expected test output.
22. The machine readable medium of claim 20, wherein the instructions for comparing the XML of the actual test output and the XML of the expected test output comprise:
submitting the XML of the actual test output and the XML of the expected test output to an XML change detection algorithm;
examining the output of the XML change detection algorithm to determine if the XML of the actual test output and the XML of the expected output are equal; and
identifying any differences between the XML of the actual test output and the XML of the expected test output.
23. The machine readable medium of claim 18, wherein the input for the unit test is captured from a production system that includes a production version of the module under test in the unit test; and further wherein the capturing of the input for the unit test includes the use of one or more of a debugger, a call trace with data, a programmable data recorder, and a source code generator.
24. The machine readable medium of claim 18, wherein the input for the unit test is captured from the same system upon which the unit test is performed; and further wherein the capturing of the input for the unit test includes the use of one or more of a debugger, a call trace with data, a programmable data recorder, and a source code generator.