Method and apparatus for testing a binding application programming interface

1. A method for testing a binding Application Programming Interface (API) on a device, wherein the binding API is bound to a native API for a device and provides different commands than the native API, the method comprising:

executing a native-API test on the device through the native API to produce a native-API test-result;

receiving the native-API test-result from the device;

sending a binding-API test to a test-agent on the device which enables the test-agent to execute the binding-API test through the binding API to produce a binding-API test-result;

receiving the binding-API test-result from the test-agent; and

comparing the native-API test-result to the binding-API test-result to determine if the binding API is functionally equivalent to the native API.

2. The method of claim 1 , wherein the device can be a resource-constrained device.

3. The method of claim 1 , wherein the native-API test-result and the binding-API test-result can include:

images;

text;

video; and

audio.

4. The method of claim 1 , wherein comparing the native-API test-result to the binding-API test-result involves comparing function calls made while executing the native-API test to function calls made while executing the binding-API test.

5. The method of claim 1 , wherein the native-API test and the API test include equivalent command flows.

6. The method of claim 1 , wherein the native API can be:

a hardware API;

a software API; and

a combination of the hardware API and the software API.

7. The method of claim 1 , wherein the test-agent facilitates executing the binding-API test by processing binding API commands, which are associated with the binding API.

8. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for testing a binding Application Programming Interface (API) on a device, wherein the binding API is bound to a native API for a device and provides different commands than the native API, the method comprising:

executing a native-API test on the device through the native API to produce a native-API test-result;

receiving the native-API test-result from the device;

sending a binding-API test to a test-agent on the device which enables the test-agent to execute the binding-API test through the binding API to produce a binding-API test-result;

receiving the binding-API test-result from the test-agent; and

comparing the native-API test-result to the binding-API test-result to determine if the binding API is functionally equivalent to the native API.

9. The computer-readable storage medium of claim 8 , wherein the device can be a resource-constrained device.

10. The computer-readable storage medium of claim 8 , wherein the native-API test-result and the binding-API test-result can include:

images;

text;

video; and

audio.

11. The computer-readable storage medium of claim 8 , wherein comparing the native-API test-result to the binding-API test-result involves comparing function calls made while executing the native-API test to function calls made while executing the binding-API test.

12. The computer-readable storage medium of claim 8 , wherein the native-API test and the API test include equivalent command flows.

13. The computer-readable storage medium of claim 8 , wherein the native API can be:

a hardware API;

a software API; and

a combination of the hardware API and the software API.

14. The computer-readable storage medium of claim 8 , wherein the test-agent facilitates executing the binding-API test by processing binding API commands, which are associated with the binding API.

15. An apparatus that tests a binding Application Programming Interface (API) on a device, wherein the binding API is bound to a native API for a device and provides different commands than the native API, the apparatus comprising:

an execution mechanism configured to execute a native-API test on the device through the native API to produce a native-API test-result;

a receiving mechanism configured to receive the native-API test-result from the device;

a sending mechanism configured to send a binding-API test to a test-agent on the device which enables the test-agent to execute the binding-API test through the binding API to produce a binding-API test-result;

wherein the receiving mechanism is further configured to receive the binding-API test-result from the test-agent; and

a comparison mechanism configured to compare the native-API test-result to the binding-API test-result to determine if the binding API is functionally equivalent to the native API.

16. The apparatus of claim 15 , wherein the device can be a resource-constrained device.

17. The apparatus of claim 15 , wherein the comparison mechanism is further configured to compare function calls made while executing the native-API test to function calls made while executing the binding-API test.

18. The apparatus of claim 15 , wherein the native API can be:

a hardware API;

a software API; and

a combination of the hardware API and the software API.

19. The apparatus of claim 15 , wherein the test-agent is configured to facilitate executing the binding-API test, and wherein the test-agent comprises a processing mechanism configured to process binding API commands, which are associated with the binding API.