System and method for testing applications

• US 8,701,092 B1
• Filed: 02/23/2012
• Issued: 04/15/2014
• Est. Priority Date: 06/22/2005
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Colcord, Brian
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): GOORAY, MARK A
• Application Number:
  US13/402,952
• Time in Patent Office: 782 Days
• Field of Search: None
• US Class Current: 717/127
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3692 for test results analysis
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs

Abstract

A system and method for testing at least one application is provided. The system comprises a test plan or script creation module for enabling a user to create at least one test plan or script for use in testing the at least one application. The system also comprises a test results module for initiating and determining test results associated with testing of the at least one application according to the at least one test plan or script. In some embodiments, the test results module determines and compares: (1) baseline test results achieved by resolving the at least one test plan or script against the application prior to the application being put to actual use, and (2) dynamic test results achieved by resolving the at least one test plan or script against the application after the application has been put to actual use.

Claims

1. A system for testing a software application associated with at least one web site or page, the system comprising:

at least one processor; and

at least one storage medium storing instructions that, when executed by the at least one processor, enables a computer to perform the following;

automatically identifying and defining objects associated with the software application and related parameters;

generating and storing at least one object map based on said identified and defined objects and their related parameters;

creating, based on said at least one object map, a test plan comprising one or more navigation steps, each navigation step comprising at least one method and at least one object associated with the software application;

determining baseline test results by resolving said test plan against the software application when the software application is known to be functioning properly;

determining regression test results by resolving said test plan against the software application subsequent to the determining of said baseline test results;

comparing said regression test results against said baseline test results to identify any flaw or failure in the software application, wherein the comparing accounts for one or more dynamic data and related changes associated with operations of the software application;

identifying and parameterizing said one of more dynamic data;

determining changes in dynamic data associated with an apparent flaw or failure in the software application identified from the comparing; and

excluding said apparent flaw or failure attributed to the parameterized dynamic data.

2. The system according to claim 1, wherein said each navigation step further comprises at least one parameter or value associated with said at least one method and/or said at least one object.

3. The system according to claim 1, wherein the baseline test results are subsequently altered based on changes in content of the at least one web site or page associated with the software application.

4. The system according to claim 1, being further configured to dynamically capture objects associated with the software application as a user or tester interacts with the software application.

5. The system according to claim 1, being further configured to automatically generate a test plan template from the at least one object map.

6. The system according to claim 1, being further configured to present a spreadsheet interface as a non-programming user interface to the system.

7. The system according to claim 6, wherein said spreadsheet interface is further configured to cooperate with a testing tool that executes the test plan.

8. The system according to claim 6, wherein said spreadsheet interface is further configured to interface with a storage device to store and access test plans.

9. A computer-implemented method for testing a software application associated with at least one web site or page, the method comprising:

identifying and defining, by at least one processor, objects associated with the software application and related parameters;

generating and storing, by at least one processor, at least one object map based on said identified and defined objects and their related parameters;

creating, by at least one processor and based on said at least one object map, a test plan comprising one or more navigation steps, each navigation step comprising at least one method and at least one object associated with the software application;

determining, by at least one processor, baseline test results by resolving said test plan against the software application when the software application is known to be functioning properly;

determining, by at least one processor, regression test results by resolving said test plan against the software application subsequent to the determining of said baseline test results; and

comparing said regression test results against said baseline test results to identify any flaw or failure in the software application, wherein the comparing accounts for one or more dynamic data and related changes associated with operations of the software application;

wherein the method further comprises;

identifying and parameterizing said one or more dynamic data;

determining changes in dynamic data associated with an apparent flat or failure in the software application identified from the comparing; and

excluding said apparent flaw or failure attributed to the parameterized dynamic data.

10. The method according to claim 9, wherein said each navigation step further comprises at least one parameter or value associated with said at least one method and/or said at least one object.

11. The method according to claim 9, further comprising:

updating said baseline test results based on changes in content of the at least one web site or page associated with the software application.

12. The method according to claim 9, further comprising:

dynamically capturing objects associated with the software application as a user or tester interacts with the software application.

13. The method according to claim 9, further comprising:

automatically generating a test plan template from the at least one object map.

14. The method according to claim 9, further comprising:

presenting a spreadsheet interface as a non-programming user interface to the system.

15. The method according to claim 14, wherein said spreadsheet interface is further configured to cooperate with a testing tool that executes the test plan.

16. The method according to claim 14, wherein said spreadsheet interface is further configured to interface with a storage device to store and access test plans.

17. A non-transitory computer readable medium containing code for testing a software application associated with at least one web site or page, the code being configured to instruct at least one processor to perform the following:

identifying and defining, by at least one processor, objects associated with the software application and related parameters;

generating and storing, by at least one processor, at least one object map based on said identified and defined objects and their related parameters;

creating, by at least one processor and based on said at least one object map, a test plan comprising one or more navigation steps, each navigation step comprising at least one method and at least one object associated with the software application;

determining, by at least one processor, baseline test results by resolving said test plan against the software application when the software application is known to be functioning properly;

determining, by at least one processor, regression test results by resolving said test plan against the software application subsequent to the determining of said baseline test results; and

comparing said regression test results against said baseline test results to identify any flaw or failure in the software application, wherein the comparing accounts for one or more dynamic data and related changes associated with operations of the software application;

identifying and parameterizing said one or more dynamic data;

determining changes in dynamic data associated with an apparent flaw or failure in the software application identified from the comparing; and

excluding said apparent flaw or failure attributed to the parameterized dynamic data.