Methods and systems for generating test information from a source code

• US 9,317,402 B2
• Filed: 03/19/2015
• Issued: 04/19/2016
• Est. Priority Date: 12/12/2011
• Status: Active Grant

• Current Assignee: Zynga Incorporated
• Original Assignee: Zynga Incorporated
• Inventors: Kuzmin, Aleksandr
• Primary Examiner(s): Lee, Marina
• Application Number:
  US14/663,321
• Publication Number:
  US 20150193333A1
• Time in Patent Office: 397 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3676 for coverage analysis
• 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/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 8/72 Code refactoring

Abstract

Systems and methods for generating test information from a source code are described. One of the methods includes accessing the source code. The method further includes receiving a modification of the source code to generate a modified source code. The modification includes one or more instructions that do not affect functions performed by executing the source code. The modification further includes one or more instructions for generating test information regarding each executable line of the source code.

Claims

1. A method for testing a source code, comprising:

receiving the source code, wherein the source code includes a plurality of executable lines and a plurality of non-executable lines, wherein each of the plurality of executable lines includes a functional statement, wherein the functional statement includes a condition for execution by a processor or includes an action for execution by the processor;

parsing the source code to identify the executable lines and the non-executable lines of the source code; and

upon identifying each of the executable lines and each of the non-executable lines, generating test information regarding each of the executable lines of the source code without testing each of the non-executable lines of the source code, wherein each of the non-executable lines is not tested by skipping each of the non-executable lines, wherein at least one of the non-executable lines defines a type of variable.

2. The method of claim 1, wherein the source code is configured to be compiled into an object code, wherein the object code is in a binary form, wherein the source code is not in the binary form.

3. The method of claim 1, wherein each of the executable lines is prepended with a collection function for collecting test information regarding the executable line, wherein each of the non-executable lines is not prepended with a collection function to avoid collecting test information regarding the non-executable line.

4. The method of claim 1, wherein each of the non-executable lines includes a comment, or is an empty line, or a definition, or a pre-processing directive, or a function prototype line, wherein the comment provides a meaning of a portion of one of the non-executable lines that has the comment, wherein the empty line does not include a character, wherein the definition names a function within the source code, wherein the pre-processing directive causes a compiler program to replace a line within the source code having a portion of the preprocessing directive with text within the processing directive, wherein the function prototype includes a name of a function, or a data type that is input to the function, or a data type that is output as a result of execution of the function.

5. The method of claim 1, wherein the action is performed when the condition is satisfied.

6. The method of claim 1, wherein the action is a logical operation or an arithmetic operation or an operation to assign a value to the variable.

7. The method of claim 1, wherein parsing the source code is performed to distinguish the executable lines from the non-executable lines.

8. The method of claim 1, wherein the test information includes coverage information, wherein the coverage information is regarding a number of times each executable line of the source code is executed during said generating the test information.

9. The method of claim 1, wherein the test information includes consumption information, wherein the consumption information is regarding a percentage of a time cycle of a hardware resource each executable line of the source code consumes during said generating the test information.

10. The method of claim 1, wherein each of the non-executable lines is ignored during said generating the test information.

11. The method of claim 1, wherein each of the non-executable lines is ignored during compilation of the source code.

12. The method of claim 1, whether the type of variable is an integer or a character.

13. The method of claim 1, wherein the source code includes a game code.

14. The method of claim 1, wherein each of the executable lines is a commentless line, a non-empty line, a definitionless line, and a function prototypeless line.

15. A computer system for generating test information from a source code, comprising:

a memory device for storing the source code; and

a processor coupled to the memory device,

wherein the processor is configured to receive the source code, wherein the source code includes a plurality of executable lines and a plurality of non-executable lines, wherein each of the plurality of executable lines includes a functional statement, wherein the functional statement includes a condition for execution by a processor or includes an action for execution by the processor,

wherein the processor is configured to parse the source code to identify the executable lines and the non-executable lines of the source code,

wherein upon identifying each of the executable lines and each of the non-executable lines, the processor is configured to generate test information regarding each of the executable lines of the source code without testing each of the non-executable lines of the source code, wherein each of the non-executable lines is not tested by skipping each of the non-executable lines, wherein at least one of the non-executable lines defines a type of variable.

16. The computer system of claim 15, wherein the processor is configured to ignore each of the non-executable lines during generation of the test information.

17. The computer system of claim 15, wherein each of the non-executable lines includes a comment, or is an empty line, or a definition, or a pre-processing directive, or a function prototype line, wherein the comment provides a meaning of a portion of one of the non-executable lines that has the comment, wherein the empty line does not include a character, wherein the definition names a function within the source code, wherein the pre-processing directive causes a compiler program to replace a line within the source code having a portion of the preprocessing directive with text within the processing directive, wherein the function prototype includes a name of a function, or a data type that is input to the function, or a data type that is output as a result of execution of the function.

18. A non-transitory computer-readable medium containing program instructions for causing a computer to perform a method of:

receiving a source code, wherein the source code includes a plurality of executable lines and a plurality of non-executable lines, wherein each of the plurality of executable lines includes a functional statement, wherein the functional statement includes a condition for execution by a processor or includes an action for execution by the processor;

parsing the source code to identify the executable lines and the non-executable lines of the source code; and

upon identifying each of the executable lines and each of the non-executable lines, generating test information regarding each of the executable lines of the source code without testing each of the non-executable lines of the source code, wherein each of the non-executable lines is not tested by skipping each of the non-executable lines, wherein at least one of the non-executable lines defines a type of variable.

19. The non-transitory computer-readable medium of claim 18, wherein each of the non-executable lines is ignored during said generating the test information.

20. The non-transitory computer-readable medium of claim 18, wherein each of the non-executable lines includes a comment, or is an empty line, or a definition, or a pre-processing directive, or a function prototype line, wherein the comment provides a meaning of a portion of one of the non-executable lines that has the comment, wherein the empty line does not include a character, wherein the definition names a function within the source code, wherein the pre-processing directive causes a compiler program to replace a line within the source code having a portion of the preprocessing directive with text within the processing directive, wherein the function prototype includes a name of a function, or a data type that is input to the function, or a data type that is output as a result of execution of the function.