Techniques for software configuration tracking

• US 7,437,717 B1
• Filed: 01/07/2004
• Issued: 10/14/2008
• Est. Priority Date: 04/12/2000
• Status: Expired due to Fees

• Current Assignee: Micro Focus IP Ltd. (Open Text Corporation)
• Original Assignee: Compuware Corporation (KKR & Co., Inc.)
• Inventors: Strickman, Michael, Cowan, Kenneth W.
• Primary Examiner(s): VU, TUAN A
• Application Number:
  US10/754,017
• Time in Patent Office: 1,742 Days
• Field of Search: 717/100, 717/105, 717115-122, 717127-137, 717/162, 707/1, 707/100, 707101-102, 707201-203
• US Class Current: 717/131
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Techniques for gathering and tracking build information are described. Builds are registered initially. When a test execution is performed, a matching build is automatically determined from those previously registered builds as matching the software under test for a particular session. This information is tabulated in a database in accordance with additional software and hardware or platform information describes the environment in which a program executes. The platform information includes software component information and system configuration information uniquely identifying a particular instance of an environment. Data stored in the database is then analyzed and available for performing queries, for example, such as regarding code volatility and determining testing associated with a particular build.

Claims

1. A computer implemented method for automatically tracking build information to determine a volatility metric between a first build of a first version of software and a second build of a second version of software, comprising:

extracting the second build by processing, for the second version of the software, one or more software modules produced using a compilation process resulting in said one or more software modules of the second version of software, wherein said second build includes at least one of;

a name field, a build number, a date and time identifier, a number of functions and modification information for the functions being associated with at least one software module as a result from said compilation process;

following extracting the second build, registering said second build by storing said second build corresponding to said second version of software in a database;

executing said second version of software;

automatically determining runtime data during execution of said second version of the software, wherein the runtime data corresponds to information extracted and registered for the second version of the software;

performing a query of the database to retrieve the second build based on the runtime data and to retrieve the first build; and

after performing the query of the database to retrieve the first build and the second build, determining a volatility metric of code change that has occurred between the first and second versions of the software, wherein determining the volatility metric includes matching portions of the first build to corresponding portions of said second build and determining at least one of;

a date and time difference, a build number difference, a number of functions added, a number of functions removed and a number of functions modified in a software module of the second version of the software in comparison to a software module of the first version of the software.

2. The method of claim 1, wherein said database that includes said build information is an object database, and the method further comprises:

creating and storing one or more objects corresponding to each of said builds; and

creating and storing one or more objects corresponding to software modules included in each of the builds.

3. The method of claim 2, further including:

creating and storing a session object corresponding to a test session of said software;

creating and storing one or more objects corresponding to software modules describing said software module information;

automatically determining a previously created build object corresponding to one of said one or more builds previously registered; and

storing an address of said previously created build object in said session object.

4. The method of claim 1, wherein subroutine calls associated with an operating system executing in said computer system are used in said gathering runtime information.

5. The method of claim 1, further comprising:

creating and storing a bug report object corresponding to a bug report, said bug report object including an address associated with said second build.

6. The method of claim 5, further including:

submitting said bug report included in a formatted electronic message;

interpreting data included in said formatted electronic message to enable said determining of said second build.

7. The method of claim 6, further including:

creating and storing another build object corresponding to a build in which said bug report is identified as being corrected; and

associating said other build object with said bug report object in said database.

8. The method of claim 1, wherein said automatically determining said runtime data further comprises:

determining said second build for which a matching build is being determined from said one or more builds registered;

determining a candidate list including one or more builds having at least one software module in common with said second build;

for each build included in said candidate list, determining if software modules included in said each build match software modules included in said second build;

for each build included in said candidate list, if there are no software modules included in said each build that have a module name and associated attributes matching a software module included in said second build, determining that said each build is not a match for said second build; and

for each build included in said candidate list, if a first of said software modules included in said each build has a module name that matches a software module included in said second build but attributes associated with said software module do not match said software module included in said second build, determining that said each build is not a match for said second build.

9. The method of claim 8, further including:

for each build included in said candidate list, determining a number of matches for software modules included in said each build having a matching module name and attributes of a software module included in said second build;

determining a valid list of one or more matching builds, each of said builds included in said valid list having a full match for software modules included in said each build with software modules included in said second build, each software module included in said each build having a corresponding matching software module included in said second build, said name and associated attributes of said each software module matching said matching software module included in said second build; and

determining a maybe list of one or more builds, each of said one or more builds included in said maybe list having at least one software module having a module name that does not have a matching software module included in said second build, said each build including at least one software module having a module name and associated attributes matching another software module included in said second build, wherein said each build has an associated number of matches.

10. The method of claim 9, further including:

if said valid list is empty, for each project, adding a build from said maybe list to said valid list in which the build added has a maximum number of matches of builds associated with said each project, a project having one or more associated builds;

performing an alternative action if said valid list is empty;

if there is only one build included in said valid list, determining that said one build matches said second build; and

if there is more than one build included in said valid list, selecting one of the more than one builds included in said valid list as being the build matching said second build.

11. The method of claim 10, further including:

selecting one or more build associated with a software project.

12. The method of claim 10, further including:

determining a matching build in accordance with a predetermined build selected from a list of more than one build previously registered.

13. A computer readable medium comprising machine executable code stored thereon for automatically tracking build information to determine a volatility metric between a first build of a first version of software and a second build of a second version of software, the computer readable medium comprising:

machine executable code for extracting the second build by processing, for the second version of the software, one or more software modules produced using a compilation process resulting in said one or more software modules of the second version of software, wherein said second build includes at least one of;

a name field, a build number, a date and time identifier, a number of functions and modification information for the functions being associated with at least one software module as a result from said compilation process;

machine executable code for registering said second build following extracting the second build by storing said second build corresponding to said second version of software in a database;

machine executable code for automatically determining runtime data during execution of said second version of the software, wherein the runtime data corresponds to information extracted and registered for the second version of the software;

machine executable code for performing a query of the database to retrieve the second build based on the runtime data and to retrieve the first build; and

machine executable code for determining a volatility metric of code change that has occurred between the first and second versions of the software after performing the query of the database to retrieve the first build and the second build, wherein determining the volatility metric includes matching portions of the first build to corresponding portions of said second build and determining at least one of;

a date and time difference, a build number difference, a number of functions added, a number of functions removed and a number of functions modified in a software module of the second version of the software in comparison to a software module of the first version of the software.

14. The computer readable medium of claim 13, wherein said database that includes said build information is an object database, and the computer program product further comprises:

machine executable code for creating and storing one or more objects corresponding to each of said builds; and

machine executable code for creating and storing one or more objects corresponding to software modules included in each of the builds.

15. The computer readable medium of claim 14, further including:

machine executable code for creating and storing a session object corresponding to a test session of said software;

machine executable code for creating and storing one or more objects corresponding to software modules describing said software module information;

machine executable code for determining automatically a previously created build object corresponding to one of said one or more builds previously registered; and

machine executable code for storing an address of said previously created build object in said session object.

16. The computer readable medium of claim 13, wherein machine executable code associated with an operating system is used in gathering runtime information.

17. The computer readable medium of claim 13, further including:

machine executable code for creating and storing a bug report object corresponding to a bug report, said bug report object including an address associated with said second build.

18. The computer readable medium of claim 17, further including:

machine executable code for submitting a bug report included in a formatted electronic message; and

machine executable code for interpreting data included in said formatted electronic message to enable determination of said second build.

19. The computer readable medium of claim 18, further including:

machine executable code for creating and storing another build object corresponding to a build in which said bug report is identified as being corrected; and

machine executable code for associating said other build object with said bug report object in said database.

20. The computer readable medium of claim 13, wherein said machine executable code for automatically determining said runtime data further comprises:

machine executable code for determining said second build for which a matching build is being determined from said one or more builds registered;

machine executable code for determining a candidate list including one or more builds having at least one software module in common with said second build;

machine executable code for determining, for each build included in said candidate list, if software modules included in said each build match software modules included in said second build;

machine executable code for determining, for each build included in said candidate list, if there are no software modules included in said each build that have a module name and associated attributes matching a software module included in said second build, determining that said each build is not a match for said second build; and

machine executable code for determining, for each build included in said candidate list, that said each build is not a match for said second build if a first of said software modules included in said each build has a module name that matches a software module included in said second build but attributes associated with said software module do not match said software module included in said second build.

21. The computer readable medium of claim 13, further including:

machine executable code for determining, for each build included in said candidate list, a number of matches for software modules included in said each build having a matching module name and attributes of a software module included in said second build;

machine executable code for determining a valid list of one or more matching builds, each of said builds included in said valid list having a full match for software modules included in said each build with software modules included in said second build, each software module included in said each build having a corresponding matching software module included in said second build, said name and associated attributes of said each software module matching said matching software module included in said second build; and

machine executable code for determining a maybe list of one or more builds, each of said one or more builds included in said maybe list having at least one software module having a module name that does not have a matching software module included in said second build, said each build including at least one software module having a module name and associated attributes matching another software module included in said second build, wherein said each build has an associated number of matches.

22. The computer readable medium of claim 21, further including:

machine executable code for adding, if said valid list is empty, for each project, a build from said maybe list to said valid list in which the build added has a maximum number of matches of builds associated with said each project, a project having one or more associated builds;

machine executable code for performing an alternative action if said valid list is empty;

machine executable code for determining that said one build matches said second build if there is only one build included in said valid list; and

machine executable code for selecting one of the more than one builds included in said valid list as being the build matching said second build if there is more than one build included in said valid list.

23. The computer readable medium of claim 22, further including:

machine executable code for selecting one or more build associated with a software project.

24. The computer readable medium of claim 22, further including:

machine executable code for determining a matching build in accordance with a predetermined build selected from a list of more than one build previously registered.