Framework for testing API of a software application

• US 8,091,072 B2
• Filed: 10/18/2007
• Issued: 01/03/2012
• Est. Priority Date: 10/18/2007
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Shah, Himesh, Gilani, Altaf, Nakhoul, Ryan, Wang, Boulland, Yacobi, Ronen
• Primary Examiner(s): KENDALL, CHUCK O
• Application Number:
  US11/874,545
• Publication Number:
  US 20090106742A1
• Time in Patent Office: 1,538 Days
• Field of Search: None
• US Class Current: 717/127
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A test executor for testing an application programming interface of a software application includes a plurality of invokers, a mapper/converter, and a comparer. The plurality of invokers includes a software application invoker and a database application invoker. The software application invoker is adapted to communicate with a software application through an application programming interface of the software application while the database application invoker is adapted to communicate with a database application through an application programming interface of the database application. The mapper/converter is in communication with the plurality of invokers. The mapper/converter converts results from at least one of the software application invoker and the database application invoker into a common data format. The comparer is in communication with the mapper/converter and compares the results in the common data format to assess the functionality of the application programming interface of the software application.

Claims

1. A test executor for testing an application programming interface of a software application, comprising:

a plurality of invokers including a software application invoker and a database application invoker, the software application invoker being adapted to communicate with a software application through an application programming interface of the software application and the database application invoker being adapted to communicate with a database application through an application programming interface of the database application, communication between the database application invoker and the database application being in parallel to communication between the software application invoker and the software application such that test results are obtained by the software application invoker independent of test results obtained by the database application invoker;

a mapper/converter in communication with the plurality of invokers, wherein the mapper/converter converts test results from at least one of the software application invoker and the database application invoker into a common data format; and

a comparer in communication with the mapper/converter, wherein the comparer compares the test results in the common data format from the mapper/converter to assess the functionality of the application programming interface of the software application.

2. A test executor for testing an application programming interface of a software application as claimed in claim 1, wherein the database application invoker includes a line of business invoker.

3. A test executor for testing an application programming interface of a software application as claimed in claim 2, wherein the mapper/converter is in communication with only the line of business invoker of the plurality of invokers.

4. A test executor for testing an application programming interface of a software application as claimed in claim 1, wherein the mapper/converter is in communication with only the database application invoker of the plurality of invokers.

5. A test executor for testing an application programming interface of a software application as claimed in claim 1, wherein the mapper/converter is in communication with only the software application invoker of the plurality of invokers.

6. A test executor for testing an application programming interface of a software application as claimed in claim 1, further comprising a test case library having predefined test case data files.

7. A test executor for testing an application programming interface of a software application as claimed in claim 6, wherein the predefined test case data files provide testing parameters/conditions to test create, read, update, delete, and query operations in the software application.

8. A test executor for testing an application programming interface of a software application as claimed in claim 6, wherein the test case library includes a test case schema that provides a sequence of test steps.

9. A test executor for testing an application programming interface of a software application as claimed in claim 6, further comprising a mapping file having a mapping schema that is read by the mapper/converter.

10. A test executor for testing an application programming interface of a software application as claimed in claim 1, further comprising a mapping file having a mapping schema that is read by the mapper/converter.

11. A test executor for testing an application programming interface of a software application as claimed in claim 1, further comprising a results logger that is in communication with the comparer.

12. A test executor for testing an application programming interface of a software application as claimed in claim 1, further comprising a test case schema that provides a sequence of test steps.

13. A test executor for testing an application programming interface of a software application as claimed in claim 1, further comprising an executor interface that is adapted for communication with external applications.

14. A test executor for testing an application programming interface of an office business application, the text executor comprising:

a software application invoker adapted to communicate with the office business application through an application programming interface of the office business application;

a line of business invoker adapted to communicate with a line of business application through an application programming interface of the line of business application, communication between the line of business invoker and the line of business application being in parallel to communication between the software application invoker and the office business application such that results are obtained by the line of business invoker independent of results obtained by the software application invoker;

a plurality of invokers including a software application invoker and a database application invoker, the software application invoker being adapted to communicate with a software application through an application programming interface of the software application and the database application invoker being adapted to communicate with a database application through an application programming interface of the database application,

a mapper/converter in communication with at least one of the software application invokers and the line of business invoker, wherein the mapper/converter converts results from at least one of the software application invoker and the line of business invoker such that results from the software application invoker and the line of business invoker are in a common data format;

a comparer in communication with the mapper/converter, wherein the comparer compares the results in the common data format from the mapper/converter to assess the functionality of the application programming interface of the software application; and

a results logger in communication with the comparer for logging results of the comparer.

15. A test executor for testing an application programming interface of an office business application as claimed in claim 14, wherein the mapper/converter converts results from each of the software application invoker and the line of business invoker.

16. A test executor for testing an application programming interface of an office business application as claimed in claim 14, further comprising a test case library having predefined test case data files, wherein the test case library is in communication with the software application invoker and the line of business invoker.

17. A test executor for testing an application programming interface of an office business application as claimed in claim 16, wherein the predefined test case data files provide testing parameters/conditions to test create, read, update, delete, and query operations in the software application.

18. A method for testing an application programming interface of a software application, the method comprising:

reading a mapping file having a mapping schema into a test executor;

reading a test case data file into the test executor, wherein a test harness provides the test case data file to the test executor;

reading a test case schema that provides a sequence of test steps;

invoking a software application invoker, wherein the software application invoker accesses a database through an application and returns results corresponding to test parameters/conditions in the test case data file;

invoking a line of business invoker, wherein the line of business invoker accesses the database and returns results corresponding to test parameters/conditions in the test case data file, communication between the line of business invoker and the database being in parallel to communication between the software application invoker and the database such that results are obtained by the line of business invoker independent of results obtained by the software application invoker;

converting the results returned from at least one of the software application invoker and the line of business invoker into a common data format in accordance with the mapping schema;

comparing results returned from the software application invoker and the line of business invoker to assess the functionality of the application programming interface of the software application; and

logging the comparison of the returned results from the software application invoker and the line of business invoker.

19. A method for testing an application programming interface of a software application as claimed in claim 18, only the results of the database application invoker are converted.

20. A method for testing an application programming interface of a software application as claimed in claim 18, further comprising reading a test case schema is provided in a test case library of the test executor.