Method and apparatus for automatic updating and testing of software

• US 7,216,343 B2
• Filed: 09/20/2002
• Issued: 05/08/2007
• Est. Priority Date: 09/20/2002
• Status: Expired due to Term

• Current Assignee: Trend Micro Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Whalley, Ian Nicholas, White, Steve Richard, Das, Rajarshi, Lassettre, Edwin Richie, Segal, Alla
• Primary Examiner(s): Steelman, Mary J.
• Application Number:
  US10/252,868
• Publication Number:
  US 20040060044A1
• Time in Patent Office: 1,691 Days
• Field of Search: 717/171, 717/176
• US Class Current: 717/168
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/3672 Test management
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A method, apparatus, and computer instructions for updating a software component. A determination is made as to whether to update the software component. The software component is updated to form an updated software component in response to a determination to update the software component. The updated software component is automatically tested. A corrective action is performed in response to a failure in testing of the updated component.

Claims

1. A method in a data processing system for updating a software component that is included in a data processing system, the method comprising the computer implemented steps of:

determining whether to update the software component;

responsive to a determination to update the software component, updating the software component to form an updated software component;

tracking information, by a primary update management component, related to particular implementations;

establishing a testing policy that specifies ones of a plurality of tests based on information related to a particular implementation;

identifying a particular implementation used in the update of the software component;

selecting ones of the plurality of tests that are specified for the particular implementation to form selected tests;

automatically performing the selected tests on the updated software component;

establishing an error procedure policy that specifies at least one of a plurality of error procedures based on a type of error;

responsive to the updated software component failing one of the selected tests, determining a type of error that occurred;

selecting one of the plurality of error procedures that is specified for the type of error that occurred;

utilizing said selected one of the plurality of error procedures to determine whether a corrective action should be performed;

in response to determining that no corrective action should be performed, leaving the updated software component unchanged; and

,

in response to determining that a corrective action should be performed, performing a corrective action according to the selected one of the plurality of error procedures.

2. The method of claim 1, wherein determining whether to update the software component comprises:

determining whether an update is present for the software component;

responsive to the update being present for the software component, determining whether the update should be applied to the software component; and

responsive to a determination to apply the update to the software component, applying the update to the software component to form the updated software component.

3. The method of claim 1, wherein the corrective action includes rolling back the updated software component to a state prior to the update being made.

4. The method of claim 1, wherein the plurality of error procedures include identifying an alternative update, rolling back the updated software component to the software component without the update, installing a different software component, not performing any corrective action, and installing the alternative update.

5. The method of claim 1, wherein the update is a new parameter for a configuration file.

6. The method of claim 1, wherein the update is to an executable file for the software component.

7. The method of claim 1 further comprising:

storing data on at least one of updates, roll backs, test results from testing of the updated component, occurrences of faults between sets of users, occurrences of faults between specific types of software components, and occurrences of faults between sets of operating systems.

8. The method of claim 1, wherein the selected test includes at least one of performance testing, on-the-fly-regression testing, unit testing, and compatibility testing.

9. The method of claim 1, wherein a first party is a source of the software update, wherein a second party provides the policy, and wherein the policy is used in determining whether to update the software component.

10. The method of claim 1, wherein determining whether to update the software component comprises:

determining whether the update is available; and

if the update is available, determining whether to apply the update using a pattern of occurrences of faults correlating to at least one of specific types of software sources, users, types of operating systems, and types of data processing systems.

11. The method of claim 1 further comprising:

determining whether the software component was successfully updated to form the updated software component; and

responsive to a failure to successfully update the software component, sending a notification of the failure.

12. The method of claim 1 further comprising:

determining whether the software component was successfully updated to form the updated software component; and

responsive to a failure to successfully update the software component, reattempting updating of the software component.

13. The method of claim 1, further comprising:

the testing policy specifying an installation test and a performance test for the particular implementation;

automatically performing the installation test to determine whether the updated software component was installed properly;

in response to determining that the updated software component was installed properly, automatically performing the performance test on the updated software component to determine whether the updated software component meets a preset metric; and

in response to determining that the updated software component does not meet the preset metric, performing the corrective action.

14. A data processing system for updating a software component, the data processing system comprising:

a bus system;

a communications unit connected to the bus system;

a memory connected to the bus system, wherein the memory includes a set of instructions; and

a processing unit connected to the bus system, wherein the processing unit executes the set of instructions to determine whether to update the software component;

update the software component to form an updated software component in response to a determination to update the software component;

track information, by a primary update management component, related to particular implementations;

establish a testing policy that specifies ones of a plurality of tests based on information related to a particular implementation;

identify a particular implementation used in updating the software component;

select ones of the plurality of tests that are specified for the particular implementation to form selected tests;

automatically perform the selected tests on the updated software component;

establish an error procedure policy that specifies at least one of a plurality of error procedures based on a type of error;

responsive to the updated software component failing one of the selected tests, determine a type of error that occurred;

select one of the plurality of error procedures that is specified for the type of error that occurred;

utilize said selected one of the plurality of error procedures to determine whether a corrective action should be performed;

in response to determining that no corrective action should be performed, leave the updated software component unchanged; and

in response to determining that a corrective action should be performed, perform a corrective action according to the selected one of the plurality of error procedures.

15. A data processing system for updating a software component, the data processing system comprising:

first determining means for determining whether to update the software component;

updating means, responsive to a determination to update the software component, for updating the software component to form an updated software component;

first tracking means for tracking information, by a primary update management component, related to particular implementations;

first establishing means for establishing a testing policy that specifies ones of a plurality of tests based on information related to a particular implementation;

identifying means for identifying a particular implementation used in the update of the software component;

first selection means for selecting ones of the plurality of tests that are specified for the particular implementation to form selected tests;

testing means for automatically performing the selected tests on the updated software component;

second establishing means for establishing an error procedure policy that specifies at least one of a plurality of error procedures based on a type of error;

second determining means, responsive to the updated software component failing one of the selected tests, for determining a type of error that occurred;

second selection means for selecting one of the plurality of error procedures that is specified for the type of error that occurred;

utilizing means for utilizing said selected one of the plurality of error procedures to determine whether a corrective action should be performed;

means responsive to determining that no corrective action should be performed, for leaving the updated software component unchanged and

performing means, responsive to determining that a corrective action should be performed, for performing a corrective action according to the selected one of the plurality of error procedures.

16. The data processing system of claim 15, wherein the first determining means further comprises:

third determining means for determining whether an update is present for the software component;

fourth determining means, responsive to the update being present for the software component, for determining whether the update should be applied to the software component; and

applying means, responsive to a determination to apply the update to the software component, for applying the update to the software component to form the updated software component.

17. The data processing system of claim 15, wherein the corrective action includes rolling back the updated software component to a state prior to the update being made.

18. The data processing system of claim 15, wherein the corrective action includes at least one of identifying an alternative update, rolling back the updated software component to the software component without the update, installing a different software component, and installing the alternative update.

19. The data processing system of claim 15, wherein the update is a new parameter for a configuration file.

20. The data processing system of claim 15, wherein the update is to an executable file for the software component.

21. The data processing system of claim 15 further comprising:

storing means for storing data on at least one of updates, roll backs, test results from testing of the updated component, occurrences of faults between sets of users, occurrences of faults between specific types of software components, and occurrences of faults between sets of operating systems.

22. The data processing system of claim 15, wherein the selected test includes at least one of performance testing, on-the-fly-regression testing, unit testing, and compatibility testing.

23. The data processing system of claim 15, wherein a first party is a source of the software update, wherein a second party provides the policy, and wherein the policy is used in determining whether to update the software component.

24. The data processing system of claim 15, wherein the first determining means comprises:

first means for determining whether the update is available; and

second means, responsive to the update being available, for determining whether to apply the update using a pattern of occurrences of faults correlating to at least one of specific types of software sources, users, types of operating systems, and types of data processing systems.

25. The data processing system of claim 15, wherein the first determining means further comprising:

third determining means for determining whether the software component was successfully updated to form the updated software component; and

sending means, responsive to a failure to successfully update the software component, for sending a notification of the failure.

26. The data processing system of claim 15, wherein the updating means is a first updating means, and further comprising:

third determining means for determining whether the software component was successfully updated to form the updated software component; and

second updating means, responsive to a failure to successfully update the software component, for reattempting updating of the software component.

27. The data processing system of claim 26, wherein the notification is sent after at least two attempted updates to the software component have failed.

28. A computer program product in a statutory tangible computer readable medium for updating a software component, the computer program product comprising:

first instructions for determining whether to update the software component;

second instructions, responsive to a determination to update the software component, for updating the software component to form an updated software component;

third instructions for tracking information, by a primary update management component, related to particular implementations; and

fourth instructions for establishing a testing policy that specifies one of a plurality of tests based on information related to a particular implementation;

fifth instructions for identifying a particular implementation used to implement the data processing system;

sixth instructions for selecting ones of the plurality of tests that are specified for the particular implementation to form selected tests;

seventh instructions for automatically performing the selected tests on the updated software component; and

eighth instructions, responsive to the updated component failing one of the selected tests, for performing a corrective action, by selecting one of a plurality of error procedures based on a type of error, from an error procedure policy.