Identification of code features potentially associated with code behavior

• US 10,565,089 B2
• Filed: 08/15/2016
• Issued: 02/18/2020
• Est. Priority Date: 08/15/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Yu, Xia, Peng, Yang, Wu, Xikang, Huang, Jieyan
• Primary Examiner(s): Zhen, Wei Y
• Assistant Examiner(s): Bourzik, Brahim
• Application Number:
  US15/237,065
• Publication Number:
  US 20180046562A1
• Time in Patent Office: 1,282 Days
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/362 Software debugging

Abstract

A first code version is received. The first code version includes a plurality of code features, such as methods or classes. A second code version is received. The second code version includes a plurality of code features. The first code version is executed. A first plurality of code features executed during the execution of the first code version are determined. A second plurality of code features differing between the first and second code versions are determined. The first and second plurality of code features are compared. An indication is provided that a code feature is potentially relevant to the code behavior if the code feature is present in the first plurality of code features and in the second plurality of code features.

Claims

1. A computing system that implements a code analysis system, the computing system comprising:

a memory;

one or more processing units coupled to the memory; and

one or more computer readable storage media storing instructions that, when loaded into the memory, cause the one or more processing units to perform operations for;

receiving a first code version, the first code version comprising a first plurality of source code features;

receiving a second code version, the second code version comprising a second plurality of source code features;

executing an executable version of the first code version, which can be the first code version;

monitoring the execution of the executable version of the first code version, the monitoring comprising determining a third plurality of source code features from the first plurality of source code features which are executed during the execution of the executable version of the first code version, the determining comprising determining classes or methods executed, called, invoked, constructed, or instantiated during execution of the executable version of the first code version;

generating a first plurality of source code signatures for the first code version from one or more source code features of the first plurality of source code features defined in source code or byte code of the first code version;

wherein at least a first source code feature of the first plurality of source code features comprises (i) a declaration of a method, function, or class, the declaration comprising a first plurality of first source code elements or a first plurality of first byte code elements of the at least a first source code feature, the first plurality of first source code elements or the first plurality of first byte code elements being selected from the group consisting of access types, return types, method names, arguments numbers, and argument types;

or (ii) a first plurality of operations, defined in source code or byte code of the at least a first source code feature, that implement a method or function; and

wherein a first source code signature of the at least a first source code feature comprises (i) a concatenation of the first plurality of first source code elements or the first plurality of first byte code elements, or a concatenation of the first plurality of operations;

or (ii) a hash value generated from a concatenation of the first plurality of first source code elements or the first plurality of first byte code elements, or a hash value generated from a concatenation of the first plurality of operations;

generating a second plurality of source code signatures for the second code version from one or more source code features of the second plurality of source code features defined in source code or byte code of the second code version;

wherein at least a second source code feature of the second plurality of source code features comprises (i) a declaration of a method, function, or class, the declaration comprising a second plurality of second source code elements or a second plurality of second byte code elements, the second plurality of second source code elements or the second plurality of second byte code elements being selected from the group consisting of access types, return types, method names, arguments numbers, and argument types;

or (ii) a second plurality of operations, defined in the source code or byte code of the at least a second code feature, that implement a method or function; and

wherein a second source code signature of the at least a second source code feature comprises (i) a concatenation of the second plurality of second source code elements or the second plurality of second byte code elements, or a concatenation of the second plurality of operations;

or (ii) a hash value generated from a concatenation of the second plurality of second source code elements or the second plurality of second byte code elements, or a hash value generated from a concatenation of the second plurality of operations;

comparing the first plurality of source code signatures with the second plurality of source code signature;

in response to determining that a third source code signature for a given source code feature of the first code version differs from a fourth source code signature for a source code feature of the second code version corresponding to the given source code feature, adding the given source code feature to a fourth plurality of source code features;

comparing the third plurality of source code features and the fourth plurality of source code features, at least a portion of the compared third plurality of source code features not directly identified by the monitoring as associated with a runtime error, wherein source code features present in both the third plurality of source code features and the fourth plurality of source code features are added to a fifth plurality of source code features; and

providing an indication that a source code feature of the fifth plurality of source code features is potentially associated with the code behavior of interest.

2. The computing system of claim 1, wherein determining the third plurality of source code features comprises analyzing a call stack associated with the execution of the executable version of the first code version.

3. The computing system of claim 1, the processing further comprising, for at least one source code feature indicated as potentially associated with the code behavior of interest:

comparing source code of the first code version associated with the at least one source code feature with source code of the second code version associated with the at least one source code feature;

displaying the first source code version with an indication of changes compared with the second source code version.

4. The computing system of claim 1, wherein a sixth plurality of source code features of the fifth plurality of source code features are indicated as potentially associated with the code behavior of interest, and the processing further comprises:

ranking source code features of the sixth plurality of source code features;

wherein the ranking is based at least in part on identities of individuals associated with changes to the sixth plurality of source code features.

5. The computing system of claim 1, wherein a sixth plurality of source code features of the fifth plurality of source code features are indicated as potentially associated with the code behavior of interest, and the processing further comprises:

ranking source code features of the sixth plurality of source code features;

wherein the sixth plurality of source code features comprise methods of one or more classes and the ranking is based at least in part on identities of the one or more classes.

6. The computing system of claim 1, wherein a sixth plurality of source code features of the fifth plurality of source code features are indicated as potentially associate with the code behavior of interest, and the processing further comprising:

ranking source code features of the sixth plurality of source code features;

wherein the sixth plurality of source code features comprise methods of one or more classes and the ranking is based at least in part on a number of changed methods associated with the one or more classes.

7. The computing system of claim 1, wherein the determining of the third plurality of source code features or the fourth plurality of source code features comprises applying at least one filter criterion, the at least one filter criterion comprising at least one class identifier.

8. The computing system of claim 1, wherein determining the third plurality of source code features comprises applying at least one filter criterion, the at least one filter criterion comprising at least one execution identifier.

9. The computing system of claim 1, wherein executing the first code version comprises:

executing a plurality of stored commands.

10. The computing system of claim 1, wherein determining a fourth plurality of code features comprises determining added source code features, deleted source code features, and modified source code features between source code or byte code of the first code version and source code or byte code of the second code version.

11. The computing system of claim 1, wherein the code behavior of interest comprises a runtime error.

12. One or more computer-readable storage media storing computer-executable instructions for causing a computing system to perform processing to identify at least one code feature potentially associated with a code behavior of interest, the processing comprising:

displaying on a graphical user interface a user interface control allowing a user to select a user-selected timeframe during which changed code may be associated with a code behavior of interest, the user interface control being useable to define a start date and an end date for the user-selected timeframe;

through the user interface control, receiving user input selecting the user-selected timeframe;

receiving a first code version of computer code, the first code version defined by source code comprising a first plurality of source code features;

executing an executable version of the first code version, which can be the first code version;

monitoring the execution of the executable version of the first code version, the monitoring comprising determining a second plurality of source code features executed during the execution of the executable version of the first code version, the determining comprising determining classes or methods defined in the source code of the first code version and executed, called, invoked, constructed, or instantiated during execution of the executable version of the first code version;

analyzing a priority of stored code versions of the computer code to determine one or more second code versions of the computer code created or modified within the user-selected timeframe by determining whether a created-on or modified-on date associated with a stored code version is within the user-selected timeframe;

for the one or more second code versions, determining a third plurality of source code features differing between the first code version and the one or more second code version by one or both of;

(i) comparing source code signatures, a source code signature being associated with one or more source code features, wherein a given source code signature is generated from one or more source code elements or byte code elements of the one or more source code features, for one or more source code features of the first code version and a given second code version, wherein if source code signatures for an associated source code feature of the one or more source code features differ between the first code version and the given second code version, and a date of the given second code version is within the user-selected timeframe, the one or more source code features are added to the third plurality of source code features;

or

(ii) comparing source code or byte code text between one or more source code features of source code or byte code for the first code version and source code or byte code of a given second code version of the one or more second code versions, wherein if a source code text or a byte code text differs between the first code version and the given second code version, and a date of the given second code version is within the user-selected timeframe, code features defined by the changed source code text or byte code text are added to the third plurality of source code features;

comparing, the second plurality of source code features and the third plurality of source code features, at least a portion of the compared third plurality of third source code features not directly identified by the monitoring as associated with a runtime error, wherein source code features present in both the second plurality of source code features and the third plurality of source code features are added to a fourth plurality of code features; and

providing an indication that a source code feature of the fourth plurality of source code features is potentially relevant to the code behavior of interest.

13. In a computing system comprising a memory and one or more processors, a method of determining methods potentially associated with a code error, the method comprising:

receiving a first code version, the first code version comprising a first plurality of source code features;

receiving a second code version, the second code version comprising a second plurality of source code features;

executing an executable version of the first code version, which can be the first code version;

monitoring the execution of the executable version of the first code version, the monitoring comprising determining a third plurality of source code features from the first plurality of source code features which are executed during the execution of the executable version of the first code version, the determining comprising determining classes or methods executed, called, invoked, constructed, or instantiated during execution of the executable version of the first code version;

generating a first plurality of source code signatures for the first code version from one or more source code features of the first plurality of source code features defined in source code or byte code of the first code version;

wherein at least a first source code feature of the first plurality of source code features comprises (i) a declaration of a method, function, or class, the declaration comprising a first plurality of first source code elements or a first plurality of first byte code elements of the at least a first source code feature, the first plurality of first source code elements or the first plurality of first byte code elements being selected from the group consisting of access types, return types, method names, arguments numbers, and argument types;

or (ii) a first plurality of operations, defined in source code or byte code of the at least a first source code feature, that implement a method or function; and

wherein a first source code signature of the at least a first source code feature comprises (i) a concatenation of the first plurality of first source code elements or the first plurality of first byte code elements, or a concatenation of the first plurality of operations;

or (ii) a hash value generated from a concatenation of the first plurality of first source code elements or the first plurality of first byte code elements, or a hash value generated from a concatenation of the first plurality of operations;

generating a second plurality of source code signatures for the second code version from one or more source code features of the second plurality of source code features defined in source code or byte code of the second code version;

wherein at least a second source code feature of the second plurality of source code features comprises (i) a declaration of a method, function, or class, the declaration comprising a second plurality of second source code elements or a second plurality of second byte code elements, the second plurality of second source code elements or the second plurality of second byte code elements being selected from the group consisting of access types, return types, method names, arguments numbers, and argument types;

or (ii) a second plurality of operations, defined in the source code or byte code of the at least a second code feature, that implement a method or function; and

wherein a second source code signature of the at least a second source code feature comprises (i) a concatenation of the second plurality of second source code elements or the second plurality of second byte code elements, or a concatenation of the second plurality of operations;

or (ii) a hash value generated from a concatenation of the second plurality of second source code elements or the second plurality of second byte code elements, or a hash value generated from a concatenation of the second plurality of operations;

comparing the first plurality of source code signatures with the second plurality of source code signature;

in response to determining that a third source code signature for a given source code feature of the first code version differs from a fourth source code signature for a source code feature of the second code version corresponding to the given source code feature, adding the given source code feature to a fourth plurality of source code features;

comparing the third plurality of source code features and the fourth plurality of source code features, at least a portion of the compared third plurality of source code features not directly identified by the monitoring as associated with a runtime error, wherein source code features present in both the third plurality of source code features and the fourth plurality of source code features are added to a fifth plurality of source code features; and

providing an indication that a source code feature of the fifth plurality of source code features is potentially associated with the code behavior of interest.

14. The method of claim 13, further comprising:

displaying on a graphical user interface a user interface control allowing a user to view query language statements generated during the executing the executable version of the first code version; and

receiving user input activating the user interface control; and

displaying content of at least one query language statement of the query language statements in response to the receiving user input.

15. The method of claim 14, wherein the displaying on the graphical user interface the user interface control and the receiving user input are carried out during the executing the executable version of the first code version.