System and method for maintaining and testing a software application
First Claim
Patent Images
1. A method for maintaining and testing a software application, said method comprising:
- generating a new test case template pertaining to a code change that was made to the software application;
after said generating the new test case template, creating standard test cases through use of the new test case template, wherein each standard test case pertains to the code change, and wherein the standard test cases includes a new test case;
selecting at least one test case from the standard test cases, wherein the at least one test case includes the new test case; and
a processor of a computer system testing the software application by using the at least one test case that was selected,wherein the method further comprises;
after said generating the new test case template and before said creating the plurality of standard test cases, saving a change history record documenting the code change;
recording variables impacted by the code change in a components field of the new test case template;
recording results of said testing the software application in a test results field of an actual test case template;
verifying that said testing the software application was successful;
after said verifying, generating a code change release record that identifies a version and release number of the software application having the code change; and
recording in the change history record a release date pertaining to the code change.
1 Assignment
0 Petitions
Accused Products
Abstract
Maintaining and testing a software application by performing regression testing uses standard reusable test cases from change history records to generate actual test cases. A new test case template is created upon saving a change history entry. A subset of the actual and new test cases is determined, and new actual test cases generated and documented from the subset. The new actual test cases are released after successful verification.
82 Citations
21 Claims
-
1. A method for maintaining and testing a software application, said method comprising:
-
generating a new test case template pertaining to a code change that was made to the software application; after said generating the new test case template, creating standard test cases through use of the new test case template, wherein each standard test case pertains to the code change, and wherein the standard test cases includes a new test case; selecting at least one test case from the standard test cases, wherein the at least one test case includes the new test case; and a processor of a computer system testing the software application by using the at least one test case that was selected, wherein the method further comprises; after said generating the new test case template and before said creating the plurality of standard test cases, saving a change history record documenting the code change; recording variables impacted by the code change in a components field of the new test case template; recording results of said testing the software application in a test results field of an actual test case template; verifying that said testing the software application was successful; after said verifying, generating a code change release record that identifies a version and release number of the software application having the code change; and recording in the change history record a release date pertaining to the code change. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer program product, comprising a physically tangible computer readable storage medium having a computer readable program code stored therein, said computer readable program code configured to be executed by a processor of a computer system to implement a method for maintaining and testing a software application, said method comprising:
-
generating a new test case template pertaining to a code change that was made to the software application; after said generating the new test case template, creating standard test cases through use of the new test case template, wherein each standard test case pertains to the code change, and wherein the standard test cases includes a new test case; selecting at least one test case from the standard test cases, wherein the at least one test case includes the new test case; and testing the software application by using the at least one test case that was selected, wherein the method further comprises; after said generating the new test case template and before said creating the plurality of standard test cases, saving a change history record documenting the code change; recording variables impacted by the code change in a components field of the new test case template; recording results of said testing the software application in a test results field of an actual test case template; verifying that said testing the software application was successful; after said verifying, generating a code change release record that identifies a version and release number of the software application having the code change; and recording in the change history record a release date pertaining to the code change. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer system comprising a processor and a computer readable memory unit coupled to the processor, said memory unit containing program code configured to be executed by the processor to implement a method for maintaining and testing a software application, said method comprising:
-
generating a new test case template pertaining to a code change that was made to the software application; after said generating the new test case template, creating standard test cases through use of the new test case template, wherein each standard test case pertains to the code change, and wherein the standard test cases includes a new test case; selecting at least one test case from the standard test cases, wherein the at least one test case includes the new test case; and testing the software application by using the at least one test case that was selected, wherein the method further comprises; after said generating the new test case template and before said creating the plurality of standard test cases, saving a change history record documenting the code change; recording variables impacted by the code change in a components field of the new test case template; recording results of said testing the software application in a test results field of an actual test case template; verifying that said testing the software application was successful; after said verifying, generating a code change release record that identifies a version and release number of the software application having the code change; and recording in the change history record a release date pertaining to the code change. - View Dependent Claims (16, 17, 18, 19, 20, 21)
-
Specification