Testing Program Code in Multiple Process Modes

• US 20130086558A1
• Filed: 09/29/2011
• Published: 04/04/2013
• Est. Priority Date: 09/29/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Li, Peng, Kaup, Amith Kamath, Merino, Manuel Tellez
• Application Number:
  US13/249,159
• Publication Number:
  US 20130086558A1
• Time in Patent Office: Days
• US Class Current: 717/128
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

The subject disclosure is directed towards testing program code in multiple process modes without developing separate test case source code for each process mode. Source code for one or more test cases is developed once in accordance with a standard template. Two or more process mode implementations associated with the one or more test cases are built using common source code. Based on a test command, one or more of the process mode implementations is selected for executing a test plan.

Claims

1. In a computing environment, a method performed at least in part on at least one processor, comprising, testing program code in multiple process modes, including compiling source code for one or more tests cases, building process mode implementations associated with the one or more test cases using common source code for each process mode, and providing one or more of the process mode implementations for running the one or more test cases on the program code.

2. The method of claim 1, wherein providing the one or more of the process mode implementations further comprises executing a test plan using the one or more of the process mode implementations.

3. The method of claim 2, wherein providing the one or more of the process mode implementations further comprises parsing a test command specifying one or more tests for the test plan.

4. The method of claim 3 further comprising selecting the one or more of the process mode implementations based on the test command.

5. The method of claim 2 further comprising adding one or more tests to the test plan.

6. The method of claim 2 further comprising adding one or more new test cases to the process mode implementations.

7. The method of claim 2, further comprising defining code coverage for executing the test plan.

8. The method of claim 1, wherein the process mode implementations comprise a user mode implementation.

9. The method of claim 8, wherein building the process mode implementations further comprises building the user mode implementation using common user mode source code and the source code for the one or more tests cases.

10. The method of claim 1, wherein the process mode implementations comprise a kernel mode implementation.

11. The method of claim 10, wherein building the process mode implementations further comprises building the kernel mode implementation using common kernel mode source code and the source code for the one or more tests cases.

12. The method of claim 1, wherein compiling the source code for the one or more tests cases further comprises modifying the source code for the one or more tests cases to reference a tracing mechanism for generating test results.

13. The method of claim 1, wherein building the process mode implementations further comprises generating the source code for the one or more tests cases using a standard template.

14. In a computing environment, a system, comprising, a testing mechanism configured to run tests on program code, the testing mechanism configured to compile test case source code and common source code into a kernel mode implementation and a user mode implementation, parse a test command into one or more arguments, generate a test plan based on the one or more arguments and a configuration file, and execute the test plan using the kernel mode implementation or the user mode implementation.

15. The system of claim 14, wherein the testing mechanism communicates input/output control (IOCTL) codes to the kernel mode implementation according to the test plan.

16. The system of claim 14, wherein the testing mechanism communicates function calls to the user mode implementation according to the test plan.

17. The system of claim 14, wherein the testing mechanism returns test results associated with executing the test plan.

18. The system of claim 14, wherein the testing mechanism generates test case source code using a standard template.

20. The one or more computer-readable media of claim 18 having further computer-executable instructions comprising:

modifying the source code for the process mode implementations to reference a tracing mechanism for generating test results.

19. One or more computer-readable media having computer-executable instructions, which when executed perform steps, comprising:

creating a standard template for one or more test cases;

generating test case source code using the standard template;

compiling source code for process mode implementations of the one or more test cases using common source code for each process mode;

filtering a configuration file using arguments of a test command to identify one or more tests to run; and

executing the one or more tests using one or more the process mode implementations.