Streamlining unit testing through hot code swapping

• US 8,799,875 B2
• Filed: 09/30/2010
• Issued: 08/05/2014
• Est. Priority Date: 09/30/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ziegler, Leo, Hardy, Vincent J.
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): MACASIANO, JOANNE GONZALES
• Application Number:
  US12/894,900
• Publication Number:
  US 20120084754A1
• Time in Patent Office: 1,405 Days
• Field of Search: 717/124, 717/135
• US Class Current: 717/135
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable

Abstract

Methods and systems are described for testing methods and other functions by swapping external functions for mock functions. A test case definition is entered by a programmer, which can specify the expected number of arguments and argument values of external function or method calls, the context state, the return value, and any expected error conditions. The test case definition is used by a function tester to automatically create mock functions, modify the target function so that it calls the mock functions, execute the target function with specified arguments and a test context, and then compare the results to expected results.

Claims

1. A method of testing functions using mock functions, the method comprising:

receiving information at a function tester specified using a declarative syntax that defines a test case definition for a target function to be tested by the function tester, the test case definition including an expected number of arguments to one or more external functions to be called in the target function and expected argument values for the expected number of arguments to be sent in a call to each of the one or more external functions from the target function;

creating, using a processor operatively coupled to a memory, a mock function for an external function to be called in the target function based on the received test case definition for the target function;

replacing the external function to be called in the target function with the mock function created based on the received test case definition for the target function;

calling the mock function in response to calling the target function;

determining whether the mock function was called with an expected number of arguments to the external function and expected argument values for the expected number of arguments defined according to the received test case definition for the target function; and

generating information indicative of a failure or success based on the determination whether the mock function was called with the expected number of arguments to the external function and the expected argument values for the expected number of arguments defined according to the received test case definition for the target function.

2. The method of claim 1 further comprising:

receiving an expected context state;

saving an original context state before calling the target function;

determining whether a context state underlying the function is the expected context state; and

restoring the original context state after calling the target function.

3. The method of claim 2 further comprising:

generating one or more error messages based on the determinations, an error message for determining whether the mock function was called with the expected number of arguments and expected argument values to the expected number of arguments defined according to the received test case definition for the target function and an error message for determining whether the context state underlying the function is the expected context state being normalized with respect to each other.

4. The method of claim 1 further comprising:

determining an expected return value for the target function based on the received test case definition for the target function; and

determining whether a value returned from calling the target function satisfies the expected return value defined according to the received test case definition for the target function.

5. The method of claim 1 further comprising:

determining an expected error condition based on the received test case definition for the target function;

attaching an error handler to the target function; and

determining whether an exception thrown while calling the target function satisfies the expected error condition defined according to the received test case definition for the target function.

6. The method of claim 5 wherein the attaching an error handler includes wrapping a try/catch wrapper around the target function.

7. The method of claim 1 wherein the replacing the external function to be called in the target function with the mock function occurs automatically in conjunction with the creating the mock function based on the received test case definition for the target function.

8. The method of claim 1 wherein the replacing occurs during code execution.

9. The method of claim 1 wherein the information indicative of a failure or success comprises one or more human-readable messages.

10. The method of claim 1 wherein the target function is a method.

11. The method of claim 1 wherein the expected number of arguments to the external function is implicit in the number of expected argument values defined according to the received test case definition for the target function.

12. The method of claim 1 wherein the target function is part of a class for a graphical shape.

13. The method of claim 1 wherein the target function is implemented in ECMAScript.

14. The method of claim 13 wherein the ECMAScript is a programming language selected from the group consisting of JavaScript, JScript, and ActiveScript.

15. The method of claim 1 wherein the operations are performed in the order shown.

16. The method of claim 1 wherein each operation is performed by the processor operatively coupled to the memory.

17. A non-transitory machine-readable storage medium embodying information indicative of instructions for causing one or more machines to perform the operations of claim 1.

18. A computer system executing instructions in a computer program, the computer program instructions comprising program code for performing the operations of claim 1.

19. A non-transitory machine-readable medium embodying information indicative of instructions for causing one or more machines to test functions using mock functions, the non-transitory machine-readable medium comprising:

code for receiving information specified using a declarative syntax that defines a test case definition for a target function to be tested, the test case definition including an expected number of arguments to one or more external functions to be called in the target function and expected argument values for the expected number of arguments to be sent in a call to each of the one or more external functions from the target function;

code for creating a mock function for an external function to be called in the target function based on the received test case definition for the target function;

code for replacing the external function to be called in the target function with the mock function created based on the received test case definition for the target function;

code for calling the target function, the target function calling the mock function;

code for determining whether the target function called the mock function with the expected number of arguments and the expected argument values for the expected number of arguments defined according to the received test case definition for the target function; and

code for generating information indicative of a failure or success report based on the determination whether the target function called the mock function with the expected number of arguments to the external function and the expected argument values for the expected number of arguments defined according to the received test case definition for the target function.

20. A computer system comprising:

at least one processor; and

a memory operatively coupled to the at least one processor and configured to store program code that configures the at least one processor to;

receive information specified using a declarative syntax that defines a test case definition for a target function to be tested by the function tester, the test case definition including an expected number of arguments to one or more external functions to be called in the target function and expected argument values for the expected number of arguments to be sent in a call to each of the one or more external functions from the target function;

create a mock function for an external function to be called in the target function based on the received test case definition for the target function;

replace the external function to be called in the target function with the mock function created based on the received test case definition for the target function;

determine whether a call to the target function called the mock function with an expected number of arguments to the external function and expected argument values for the expected number of arguments defined according to the received test case definition for the target function; and

generate information indicative of a failure or success report based on the determination whether the call to the target function called the mock function with the expected number of arguments to the external function and the expected argument values for the expected number of arguments defined according to the received test case definition for the target function.