TESTING DISTRIBUTED COMPONENTS

• US 20070277154A1
• Filed: 05/23/2006
• Published: 11/29/2007
• Est. Priority Date: 05/23/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Badwe, Ashutosh M.
• Application Number:
  US11/419,901
• Publication Number:
  US 20070277154A1
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

The present invention extends to methods, systems, and computer program products for testing distributed components. A test case definition indicates how APIs are to be called to test components of a distributed system. A test driver can execute the test case definition to invoke the APIs. Results of the APIs can be stored. A test case definition can use output from an API testing one distributed component as input to another API for testing a different distributed component. Accordingly, end to end integration testing is possible for computing functionality that spans multiple components of a distributed system

Claims

1. At a computer system, a method for testing components of a distributed system, the method comprising:

an act of accessing a test case definition that defines test directives for testing a plurality of different components in the distributed system, including at least first and second interconnected components;

an act of accessing a first test directive from the test case definition file;

an act of identifying that the first test directive is directed to an API included in a first test library, APIs included in the first test library configured to test the functionality of the first component;

an act of dynamically invoking the first API with parameters included in the first test directive to test the functionality of the first component;

an act of receiving results of the first API testing the first component;

an act of accessing a second test directive from the test case definition file;

an act of identifying that the second test directive is directed to an API included in a second different test library, APIs included in the second different test library configured to test the functionality of the second component;

an act of dynamically invoking the second API with parameters included in the second test directive to test the functionality of the second component; and

an act of receiving results of the second API testing the first component.

2. The method as recited in claim 1, wherein the act of accessing a test case definition that defines test directives for testing a plurality of different components comprises an act of accessing a test case definition that defines test directives in a specified format, the specified format selected from among plain text, XML instructions, and an interpretable programming language.

3. The method as recited in claim 1, wherein the act of accessing a first test directive from the test case definition file comprises an act of accessing a test directive that identifies an API and includes parameters for calling the API.

4. The method as recited in claim 1, wherein the act of dynamically invoking the first API with parameters included in the first test directive includes an act of using reflection to access metadata indicating how the first API is to be invoked.

5. The method as recited in claim 1, wherein the act of dynamically invoking the first API with parameters included in the first test directive includes an act of invoking the first API with a parameter that was obtained from a hash table.

6. The method as recited in claim 1, wherein the act of dynamically invoking the first API to test the functionality of the first component comprises an act dynamically invoking the first API to test the functionality of a component selected from among an Internet Information Services component, a Web server component, a Database component, and an Operating System component.

7. The method as recited in claim 1, further comprising:

an act of storing results of the first API testing the first component.

8. The method as recited in claim 7, wherein the act of dynamically invoking the second API with parameters included in the second test directive comprises an act of invoking the second API with a parameter included in the stored results of testing the first component.

9. The method as recited claim 1, further comprising:

an act of invoking one or more other APIs to perform integrated end to end testing of the components of the distributed system, including testing at least the first and second components.

10. The method as recited in claim 1, further comprising:

an act of accessing the first test library prior to creation of the test case definition;

an act of discovering exposed APIs and corresponding parameters included in the first test library; and

an act of storing information for calling the exposed APIs with the corresponding parameters from a test case definition.

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

an act of presenting a list of the APIs for testing the first component at at a user-interface;

an act of receiving a selection of the first API from among the list of APIs for testing the first component; and

an act of including a test directive to invoke the first API in the test case definition.

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

an act of accessing available test case definition instructions prior to creation of the test case definition; and

an act of storing available test case definition instructions.

15. The method as recited in claim 7, wherein computer-executable instructions that, when executed, cause the computer system to dynamically invoke the second API with parameters included in the second test directive to test the functionality of the second component comprise computer-executable instructions that, when executed, cause the computer system to invoke the second API with a parameter from the stored results of testing the first component.

13. A computer program product for use at a computer system, the computer program product for implementing a method for testing components of a distributed system, the computer program product comprising one or more computer-readable storage media have stored thereon computer-executable instructions that, when executed at the computer system, cause the computer system to perform the following:

access a test case definition that defines test directives for testing a plurality of different components in the distributed system, including at least first and second interconnected components;

access a first test directive from the test case definition file;

identify that the first test directive is directed to an API included in a first test library, APIs included in the first test library configured to test the functionality of the first component;

dynamically invoke the first API with parameters included in the first test directive to test the functionality of the first component;

receive results of the first API testing the first component;

access a second test directive from the test case definition file;

identify that the second test directive is directed to an API included in a second different test library, APIs included in the second different test library configured to test the functionality of the second component;

dynamically invoke the second API with parameters included in the second test directive to test the functionality of the second component; and

receiving results of the second API testing the first component.

14. The computer program product as recited in claim 13, further comprising computer-executable instructions that, when executed at the computer system, cause the computer system to store results of the first API testing the first component.

16. At a computer system, a method for creating a test case definition for testing a distributed system, the method comprising:

an act of accessing one or more test libraries including exposed APIs for testing components of the distributed system;

an act of discovering the exposed APIs;

an act of storing information indicating how the exposed APIs are to be invoked;

an act of presenting a map of the distributed system along with a list of available APIs per distributed component at a user-interface;

an act of receiving a user selection indicating that a specified API is to be called to test a component of the distributed system; and

an act of automatically utilizing the stored information to create a test directive appropriately calling the API such that the user is relieved from having to know how to create the test directive.

17. The method as recited in claim 16, further comprising:

an act of accessing available test case definition instructions; and

an act of storing available test case definition instructions.

18. The method as recited in claim 17, wherein the act of accessing available test case definition instructions comprises an act of accessing XML instructions that can be processed by a test driver to invoke API calls for testing components of the distributed system.

19. The method as recited in claim 18, wherein the act of accessing XML instructions that can be processed by a test driver to invoke API calls for testing components of the distributed system comprises an act of accessing XML instructions that can invoke an API to test a component using input values that were output values of a prior API call.

20. The method as recited in claim 16, further comprising:

an act of a receiving a user-entered execute command; and

an act of sending the test directive to a test driver for execution in response to the receiving a user-entered execute command