Integrated system and method for validating the functionality and performance of software applications

• US 7,895,565 B1
• Filed: 03/15/2006
• Issued: 02/22/2011
• Est. Priority Date: 03/15/2006
• 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: Rheingans, Alex, Petlickijne, Judit, Frank, Michael E., Hudgons, Morrisha
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): Wei; Zheng
• Application Number:
  US11/375,043
• Time in Patent Office: 1,805 Days
• Field of Search: None
• US Class Current: 717/106
• CPC Class Codes: G06F 11/3672 Test management
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases

Abstract

The system and method presented provides a multi-phase, end-to-end integrated process for testing application software using a standard software testing tool. The system and method involve integrating the functional, automated regression and performance phases of software application testing by leveraging deliverables at each phase so that the deliverables may be efficiently reused in subsequent test phases. Deliverables such as functional and technical test conditions and manual test scripts are used as inputs for each phase of the integrated tests. The use of leveraged requirements-based deliverables between test phases significantly reduces much of the repetitive testing typically associated with functionality and performance testing and minimizes repetition of testing errors discovered in earlier test phases. This integrated system and method for validating the functionality and performance of software applications by leveraging deliverables provides enhanced efficiencies, test procedure consistency throughout multiple test phases, consistent test results and high quality software applications.

Claims

1. An integrated method for validating the functionality and performance of software applications through multiple test phases using a common set of business requirements-based manual test scripts, the method comprising the steps of:

identifying functional and technical requirements from the business requirements for the software application;

deriving functional and technical test conditions in a functional test phase that are based on the identified functional and technical requirements;

creating manual test scripts based on the functional and technical test conditions using a standard software testing tool accessed through a computer workstation, wherein the manual test scripts are created in the functional test phase;

executing the manual test scripts and generating test results during the functional test phase using the standard software testing tool;

selecting a first subset of manual test scripts from the manual test scripts that can be used to automate testing during an automated regression test phase;

creating automated regression tests based on the first subset of manual test scripts, wherein creating automated regression tests comprises;

reviewing screens used for each script from the first subset of manual test scripts;

identifying object types on each of the screens;

identifying actions for each object type identified on each of the screens;

creating reusable functions for each action identified;

identifying identifiers for each unique object of the identified object types;

creating an XML object repository that contains reusable XML objects;

creating reusable automated functions based on the reusable functions and the reusable XML objects;

grouping reusable automated functions to create grouped reusable automated functions; and

creating automated test scripts based on the grouped reusable automated functions, and

executing automated regression tests and generating test results during the automated regression test phase using the standard software testing tool.

2. The method as recited in claim 1, further comprising the steps of:

selecting a second subset of manual test scripts from the manual test scripts that can be used during a performance test phase;

creating performance tests based on the second subset of manual test scripts; and

executing performance tests and generating test results during the performance test phase using the standard software testing tool.

3. The method as recited in claim 1, further comprising the step of evaluating the test results from the manual test scripts execution in the functional test phase for at least two test cycles and validating the results before selecting a first or second subset of manual test scripts to be used for subsequent test phases.

4. The method as recited in claim 1, further comprising the step of evaluating the test results from the automated regression tests executed during the automated test phase.

5. The method as recited in claim 2, wherein the step of creating performance tests based on the second subset of manual test scripts further comprises the steps of:

identifying key business transactions by using the second subset of manual test scripts, reviewing business requirements and using a transaction risk-based selection process; and

implementing script standards, wherein the script standards include the steps of developing a single script, managing script based workflow, centralizing application functions, validating context sensitive data, and centralizing error handling.

6. The method as recited in claim 2, wherein the step of creating performance tests based on the second subset of manual test scripts further comprises the steps of:

reviewing system requirements;

defining user scenarios;

defining test data requirements;

defining environment requirements; and

creating performance test data.

7. The method as recited in claim 2, further comprising the step of evaluating test results from the performance tests executed during the performance test phase.

8. The method as recited in claim 7, wherein the step of evaluating test results from the performance tests further comprises the steps of remediating performance defects, executing performance tests and generating results.

9. The method as recited in claim 2, further comprising the steps of:

reviewing final performance test results and signing off on the performance test results.

10. An integrated method for validating the functionality and performance of software applications in the functional and performance test phases using a common set of business requirements-based manual test scripts, the method comprising the steps of:

identifying functional and technical requirements based on the business requirements for the software application;

deriving functional and technical test conditions based on the identified functional and technical requirements in a functional test phase;

creating manual test scripts based on the functional and technical test conditions using a standard software testing tool accessed through a computer workstation;

executing the manual test scripts during the functional test phase using the standard software testing tool to execute the manual test scripts;

selecting a subset of manual test scripts from the manual test scripts that can be used during a performance test phase;

creating performance tests based on the subset of manual test scripts, wherein creating performance tests comprises;

reviewing screens used for each script from the first subset of manual test scripts;

identifying object types on each of the screens;

identifying actions for each object type identified on each of the screens;

creating reusable functions for each action identified;

identifying identifiers for each unique object of the identified object types;

creating an XML object repository that contains reusable XML objects;

creating reusable automated functions based on the reusable functions and the reusable XML objects;

grouping reusable automated functions to create grouped reusable automated functions; and

creating performance tests based on the grouped reusable automated functions, and

executing the performance tests during performance test phase and generating test results using the standard software testing tool.

11. The method as recited in claim 10, wherein the step of creating performance tests based on the subset of manual test scripts further comprises the steps of:

identifying key business transactions by using the subset of manual test scripts,

reviewing business requirements and using a transaction risk-based selection process; and

implementing script standards that include the steps of developing a single script, managing script based workflow, centralizing application functions, validating context sensitive data, and centralizing error handling.

12. An integrated system for validating the functionality and performance of software applications through multiple test phases using a common set of business requirements-based manual test scripts, the system comprising:

a functional test phase module configured for identifying functional and technical requirements from the business requirements for the software application, deriving functional and technical test conditions in a functional test phase that are based on the identified functional and technical requirements, creating manual test scripts based on the functional and technical test conditions using a standard software testing tool accessed through a computer workstation, wherein the manual test scripts are created in the functional test phase, and executing the manual test scripts and generating test results during the functional test phase using the standard software testing tool; and

an automated regression test phase module configured for selecting a first subset of manual test scripts from the manual test scripts that can be used to automate testing during an automated regression test phase, creating automated regression tests based on the first subset of manual test scripts, executing automated regression tests and generating test results during the automated regression test phase using the standard software testing tool, wherein the automated regression test phase module is further configured for reviewing screens used for each script from the first subset of manual test scripts, identifying object types on each of the screens, identifying actions for each object type identified on each of the screens, creating reusable functions for each action identified, identifying identifiers for each unique object of the identified object types, creating an XML object repository that contains reusable XML objects, creating reusable automated functions based on the reusable functions and the reusable XML objects, grouping reusable automated functions to create grouped reusable automated functions and creating automated test scripts based on the grouped reusable automated functions.

13. The system as recited in claim 12, further comprising:

a performance test phase module configured for selecting a second subset of manual test scripts from the manual test scripts that can be used during a performance test phase, creating performance tests based on the second subset of manual test scripts and executing performance tests and generating test results during the performance test phase using the standard software testing tool.

14. The system as recited in claim 12, wherein the functional test phase module is further configured for evaluating the test results from the manual test scripts execution in the functional test phase for at least two test cycles and validating the results before selecting a first or second subset of manual test scripts to be used for subsequent test phases.

15. The system as recited in claim 12, wherein the automated regression test phase module is further configured for evaluating the test results from the automated regression tests executed during the automated test phase.

16. The system as recited in claim 13, wherein the performance test phase module is further configured for identifying key business transactions by using the second subset of manual test scripts, reviewing business requirements and using a transaction risk-based selection process and implementing script standards based on a single script, a script based workflow management, centralized application functions, context sensitive data validation, and centralized error handling.

17. The system as recited in claim 13, wherein the performance test phase module is further configured for evaluating test results from the performance tests executed during the performance test phase.

18. The system as recited in claim 17, wherein the performance test phase module is further configured for evaluating test results from the performance tests, wherein evaluating includes remediating performance defects, executing performance tests and generating results.