Software and associated hardware regression and compatibility testing system

• US 9,740,473 B2
• Filed: 08/26/2015
• Issued: 08/22/2017
• Est. Priority Date: 08/26/2015
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Kumar, Amit, Kumar, Vivek, Kumar, Hitendra, Baghel, Purushottam
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Huynh, Tina
• Application Number:
  US14/836,215
• Publication Number:
  US 20170060560A1
• Time in Patent Office: 727 Days
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44589 Program code verification, e.g. Java bytecode verification, proof-carrying code high-level semantic checks G06F8/43; testing and debugging software G06F11/36

Abstract

The present disclosure describes testing regression and compatibility of software and associated hardware. Embodiments herein disclosed receive an indication from a user to test the regression and the compatibility of proposed software; access software files related to installation of the proposed software; present a verification interface to the user, wherein the verification interface includes various validation functions for validating entries created or updated along with the proposed software being installed or uninstalled, such as a registry entry, a log file entry, an Add or Remove Programs entry, and the like, wherein when each of the validation functions is selected, the system automatically determines if the corresponding entry for installation or uninstallation of the proposed software is successful. Embodiments herein disclosed further receive an indication from the user for selection of the validation functions and present to the user an indication of success of the validation of the entries.

Claims

1. A system for testing regression and compatibility of software and hardware, the system comprising:

one or more memory devices having computer readable program code stored thereon; and

one or more processing devices operatively coupled to the one or more memory devices, wherein the one or more processing devices are configured to execute the computer readable program code to;

receive a request from a user to install proposed software on a virtual system;

install the proposed software on the virtual system and present a compatibility testing application to the user based on receiving the request from the user;

receive an indication from the user to test the regression and the compatibility of the installed proposed software with other software and associated hardware, wherein the indication is a reference to the installed proposed software being changed;

access software files related to the installed proposed software based on the indication received from the user;

present a verification interface associated with the compatibility testing application to the user on a user computer system, wherein the verification interface comprises;

a registry key and a log file automatically populated in response to accessing software files related to the installed proposed software;

a registry key validation function associated with the registry key, wherein when the registry key validation function is selected the virtual system automatically determines whether (a) the registry key is generated upon installation of the proposed software or (b) reset upon uninstallation of the proposed software;

a log file validation function associated with the log file, wherein when the log file validation function is selected the virtual system automatically determines whether the log file includes (a) an indication of no error or (b) an indication of an error;

an Add or Remove Programs (ARP) validation function, wherein when the ARP validation function is selected the virtual system automatically determines whether (a) an ARP entry is found successfully or (b) no ARP entry is found;

a dependency validation function, wherein when the dependency validation function is selected the virtual system automatically determines whether (a) the proposed software has pre-requisite or post requisite software that has been successfully installed or (b) the proposed software has pre-requisite or post requisite software that has not been successfully installed;

receive, from the verification interface, a first selection of the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

in response to receiving the first selection, execute the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

determine that the proposed software has been installed successfully based on;

determining, based on the execution of the registry key validation function, that the registry key is generated upon installation of the proposed software;

determining, based on the execution of the log file validation function, the indication of no error;

determining, based on the execution of the ARP validation function, that the ARP entry is found successfully; and

determining, based on the execution of the dependency validation function, that the installed proposed software has the pre-requisite or the post requisite software that has been successfully installed;

in response to determining that the proposed software has been installed successfully, present an indication of success of the validation of the registry key, the log file, the ARP entry, and the pre-requisite or the post requisite software to the user on the user computer system;

receive a second request from the user to uninstall the installed proposed software from the virtual system;

uninstall the proposed software and present the compatibility testing application to the user on the user computer system based on receiving the second request from the user;

present the verification interface to the user on the user computer system;

receive, from the verification interface, a second selection of the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

determine that the proposed software has been uninstalled successfully based on;

determining, based on the execution of the registry key validation function, that the registry key is reset upon installation of the proposed software;

determining, based on the execution of the log file validation function, the indication of no error;

determining, based on the execution of the ARP validation function, that the ARP entry is found successfully; and

determining, based on the execution of the dependency validation function, that the proposed software has the pre-requisite or the post requisite software that has been successfully installed;

in response to determining that the proposed software has been uninstalled successfully, present a second indication of success of the validation of the registry key, the log file, and the ARP entry to the user on the user computing system.

2. The system of claim 1, wherein the verification interface further comprises:

an open record function, wherein when the open record function is selected the system receives information about the proposed software, wherein the information comprises a version number and package type of the proposed software.

3. The system of claim 1, wherein the verification interface further comprises:

a purpose function, wherein when the purpose function is selected the virtual system receives an indication of a purpose of the proposed software.

4. The system of claim 1, wherein the verification interface further comprises:

an upgrade check function, wherein when the upgrade check function is selected the virtual system checks a previous software version registry key to determine if a previous software version was installed before the proposed software was installed.

5. The system of claim 1, wherein the verification interface further comprises:

a shortcut test function, wherein when the shortcut test function is selected the virtual system determines and displays a default path of a shortcut of the proposed software.

6. The system of claim 1, wherein the verification interface is utilized to test both the installation and uninstallation of the proposed software on multiple domains and on multiple platforms.

7. A computer program product for testing regression and compatibility of software and hardware, the computer program product comprising a non-transitory computer readable medium comprising computer readable instructions, the instructions comprising instructions for:

receive a request from a user to install proposed software on a virtual system;

install the proposed software on the virtual system and present a compatibility testing application to the user based on receiving the request from the user;

receiving an indication from the user to test the regression and the compatibility of the installed proposed software with other software and associated hardware, wherein the indication is a reference to the installed proposed software being changed;

accessing software files related to the installed proposed software based on the indication received from the user;

presenting a verification interface associated with the compatibility testing application to the user on a user computer system, wherein the verification interface comprises;

a registry key and a log file automatically populated in response to accessing software files related to the installed proposed software;

a registry key validation function associated with the registry key, wherein when the registry key validation function is selected the virtual system automatically determines whether (a) the registry key is generated upon installation of the proposed software or (b) reset upon uninstallation of the proposed software;

a log file validation function associated with the log file, wherein when the log file validation function is selected the virtual system automatically determines whether the log file includes (a) an indication of no error or (b) an indication of an error;

an Add or Remove Programs (ARP) validation function, wherein when the ARP validation function is selected the virtual system automatically determines whether (a) an ARP entry is found successfully or (b) no ARP entry is found;

a dependency validation function, wherein when the dependency validation function is selected the virtual system automatically determines whether (a) the proposed software has pre-requisite or post requisite software that has been successfully installed along with the proposed software or (b) the proposed software has pre-requisite or post requisite software that has not been successfully installed;

receiving, from the verification interface, a first selection of the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

in response to receiving the first selection, executing the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

determining that the proposed software has been installed successfully based on;

determining, based on the execution of the registry key validation function, that the registry key is generated upon installation of the proposed software;

determining, based on the execution of the log file validation function, the indication of no error;

determining, based on the execution of the ARP validation function, that the ARP entry is found successfully; and

determining, based on the execution of the dependency validation function, that the installed proposed software has the pre-requisite or the post requisite software that has been successfully installed;

in response to determining that the proposed software has been installed successfully, presenting an indication of success of the validation of the registry key, the log file, the ARP entry, and the pre-requisite or the post requisite software to the user on the user computer system;

receiving a second request from the user to uninstall the installed proposed software from the virtual system;

uninstalling the proposed software and presenting the compatibility testing application to the user on the user computer system based on receiving the second request from the user;

presenting the verification interface to the user on the user computer system;

receiving, from the verification interface, a second selection of the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

determining that the proposed software has been uninstalled successfully based on;

determining, based on the execution of the registry key validation function, that the registry key is reset upon installation of the proposed software;

determining, based on the execution of the log file validation function, the indication of no error;

determining, based on the execution of the ARP validation function, that the ARP entry is found successfully; and

determining, based on the execution of the dependency validation function, that the proposed software has the pre-requisite or the post requisite software that has been successfully installed;

in response to determining that the proposed software has been uninstalled successfully, presenting a second indication of success of the validation of the registry key, the log file, and the ARP entry to the user on the user computing system.

8. The computer program product of claim 7, wherein verification interface further comprises:

an upgrade check function, wherein when the upgrade check function is selected the virtual system checks a previous software version registry key to determine if a previous software version was installed before the proposed software was installed.

9. The computer program product of claim 7, wherein the verification interface further comprises:

a shortcut test function, wherein when the shortcut test function is selected the virtual system determines and displays a default path of a shortcut of the proposed software.

10. The computer program product of claim 7, wherein the verification interface is utilized to test both the installation and uninstallation of the proposed software on multiple domains and on multiple platforms.

11. A computer implemented method for testing regression and compatibility of software and hardware, said computer implemented method comprising:

receiving, via a processing device, a request from a user to install proposed software on a virtual system;

installing, via a processing device, the proposed software on the virtual system and present a compatibility testing application to the user based on receiving the request from the user;

receiving, via a processing device, an indication from the user to test the regression and the compatibility of the installed proposed software with other software and associated hardware, wherein the indication is a reference to the installed proposed software being change;

accessing, via a processing device, software files related to the installed proposed software based on the indication received from the user;

presenting, via a processing device, a verification interface associated with the compatibility testing application to the user on a user computer system, wherein the verification interface comprises;

a registry key and a log file automatically populated in response to accessing software files related to the installed proposed software;

a registry key validation function associated with the registry key, wherein when the registry key validation function is selected the virtual system automatically determines whether (a) the registry key is generated upon installation of the proposed software or (b) reset upon uninstallation of the proposed software;

a log file validation function associated with the log file, wherein when the log file validation function is selected the virtual system automatically determines whether the log file includes (a) an indication of no error or (b) an indication of an error;

an Add or Remove Programs (ARP) validation function, wherein when the ARP validation function is selected the virtual system automatically determines whether (a) an ARP entry is found successfully or (b) no ARP entry is found;

a dependency validation function, wherein when the dependency validation function is selected the virtual system automatically determines whether (a) the proposed software has pre-requisite or post requisite software that has been successfully installed or (b) the proposed software has pre-requisite or post requisite software that has not been successfully installed;

receiving from the verification interface, via a processing device, a first selection of one or more of the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

in response to receiving the first selection, executing, via a processing device, the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

determining, via a processing device, that the proposed software has been installed successfully based on;

determining, based on the execution of the registry key validation function, that the registry key is generated upon installation of the proposed software;

determining, based on the execution of the log file validation function, the indication of no error;

determining, based on the execution of the ARP validation function, that the ARP entry is found successfully; and

determining, based on the execution of the dependency validation function, that the installed proposed software has the pre-requisite or the post requisite software that has been successfully installed;

in response to determining that the proposed software has been installed successfully, presenting, via a processing device, an indication of success of the validation of the registry key, the log file, the ARP entry, and the pre-requisite or the post requisite software to the user on the user computer system;

receiving, via a processing device, a second request from the user to uninstall the installed proposed software from the virtual system;

uninstalling, via a processing device, the proposed software and presenting, via a processing device, the compatibility testing application to the user on the user computer system based on receiving the second request from the user;

presenting, via a processing device, the verification interface to the user on the user computer system;

receiving from the verification interface, via a processing device, a second selection of the registry key validation function, the log file validation function, the ARP validation function, and the dependency validation function;

determining, via a processing device, that the proposed software has been uninstalled successfully based on;

determining, based on the execution of the registry key validation function, that the registry key is reset upon installation of the proposed software;

determining, based on the execution of the log file validation function, the indication of no error;

determining, based on the execution of the ARP validation function, that the ARP entry is found successfully; and

determining, based on the execution of the dependency validation function, that the proposed software has the pre-requisite or the post requisite software that has been successfully installed;

in response to determining that the proposed software has been uninstalled successfully, presenting, via a processing device, a second indication of success of the validation of the registry key, the log file, and the ARP entry to the user on the user computing system.

12. The computer implemented method of claim 11, wherein the verification interface further comprises:

an upgrade check function, wherein when the upgrade check function is selected the virtual system checks a previous software version registry key to determine if a previous software version was installed before the proposed software was installed.

13. The computer implemented method of claim 11, wherein the verification interface further comprises:

a shortcut test function, wherein when the shortcut test function is selected the virtual system determines and displays a default path of a shortcut of the proposed software.

14. The computer implemented method of claim 11, wherein the verification interface is utilized to test both the installation and uninstallation of the proposed software on multiple domains and on multiple platforms.