Software development kit testing

• US 9,292,416 B2
• Filed: 10/12/2012
• Issued: 03/22/2016
• Est. Priority Date: 10/12/2012
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Gibbens, David, Krueger, Nicholas, McDonald, Sean, Rens, Scott, Dow, Travis
• Primary Examiner(s): KENDALL, CHUCK O
• Application Number:
  US13/650,555
• Publication Number:
  US 20140109057A1
• Time in Patent Office: 1,257 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

In a method of software development kit (SDK) testing, a graphical user interface is provided for initializing a test of an SDK. An application is created to run against the SDK. The output of the SDK is verified.

Claims

1. A non-transitory computer readable storage medium comprising instructions stored thereon which, when executed, cause a computing system to perform a method of software development kit (SDK) testing, said method comprising:

presenting a graphical user interface for initializing a test of an SDK;

creating an application to run against said SDK;

verifying an output of said SDK;

testing callbacks from said SDK back to entry points in said application; and

testing a set of callbacks from said SDK to said application without regard to a sequence.

2. The non-transitory computer readable storage medium of claim 1, further comprising instructions for:

invoking each entry point into an SDK, wherein said invoking comprises providing all parameters that an entry point requires.

3. The non-transitory computer readable storage medium of claim 1, further comprising instructions for:

testing positive interactions with said SDK.

4. The non-transitory computer readable storage medium of claim 1, further comprising instructions for:

testing negative interactions with said SDK.

5. The non-transitory computer readable storage medium of claim 1, wherein testing callbacks further comprises:

testing parameter values generated by said SDK passed to said callbacks.

6. The non-transitory computer readable storage medium of claim 1, wherein testing callbacks further comprises:

testing said sequence of callbacks that said SDK makes to said application.

7. The non-transitory computer readable storage medium of claim 1, wherein testing callbacks further comprises:

testing that said SDK does not make particular callbacks to said application.

8. The non-transitory computer readable storage medium of claim 1, wherein said creating an application to run against said SDK comprises:

binding natural language to an application programming interface (API) intercept.

9. The non-transitory computer readable storage medium of claim 1, wherein said SDK comprises an action for every entry point into said SDK.

10. The non-transitory computer readable storage medium of claim 1, wherein said application to run against said SDK is similar to an original equipment manufacturer (OEM) application.

11. A method of software development kit (SDK) testing, said method comprising:

presenting a graphical user interface for initializing a test of an SDK;

creating an application to run against said SDK;

verifying an output of said SDK;

testing callbacks from said SDK back to entry points in said application; and

testing a set of callbacks from said SDK to said application without regard to a sequence.

12. The method as recited in claim 11, further comprising:

invoking each entry point into an SDK, wherein said invoking comprises providing all parameters that an entry point requires.

13. The method as recited in claim 11, further comprising:

testing negative interactions with said SDK.

14. The method as recited in claim 11, further comprising:

testing positive interactions with said SDK.

15. The method as recited in claim 11, wherein testing callbacks further comprises:

testing parameter values generated by said SDK passed to said callbacks.

16. The method as recited in claim 11, wherein testing callbacks further comprises:

testing said sequence of callbacks that said SDK makes to said application.

17. The method as recited in claim 11, wherein testing callbacks further comprises:

testing that said SDK does not make particular callbacks to said application.

18. The method as recited in claim 11, wherein said creating an application to run against said SDK comprises:

binding natural language to an application programming interface (API).

19. The method as recited in claim 11, wherein said SDK comprises an action for every entry point into said SDK.

20. The method as recited in claim 11, wherein said application to run against said SDK is similar to an original equipment manufacturer (OEM) application.

21. A software development kit (SDK) testing framework comprising:

a computing environment;

framework layer disposed in said computing environment and operable to perform a test on an SDK;

a custom action layer disposed in said computing environment;

at least one fixture layer disposed in said computing environment and operable to communicate with said framework layer and said custom action layer;

a test layer disposed in said computing environment and configured to communicate with said custom action layer; and

an SDK testing layer that is operable to create an application to run against said SDK;

wherein said framework layer is operable to test callbacks from said SDK back to entry points in said application and test a set of callbacks from said SDK to said application without regard to a sequence.

22. The computing environment of claim 21, wherein said framework layer to perform a test on an SDK is operable to test for positive and negative interactions.