System and method for functional test case generation of end-to-end business process models

Patent metadata

Field	Value
Publication number	US-10223246-B2
Application number	US-201313946249-A
Country	US
Kind code	B2
Filing date	Jul 19, 2013
Priority date	Jul 30, 2012
Publication date	Mar 5, 2019
Grant date	Mar 5, 2019

Abstract

A system, medium and method for testing an end-to-end software application is disclosed. A structured business process model (BPM) representative of a set of business requirements for an end-to-end software application to be tested is first generated. The generated structured BPM is validated in association with one or more validation rules. A functional flow layout representative of a node structure embodying all possible scenarios to be handled by the software application is then generated. A plurality of functional flow paths is identified from the functional flow layout, wherein each functional flow path is associated with one or more corresponding scenarios of the possible scenarios. One or more test cases for each identified functional flow path is then generated.

First claim

What is claimed is:

1. A method for testing an end-to-end software application having a plurality of functionalities, the method comprising:
generating, by an application testing computing device, a structured business process model (BPM) file representative of a set of business requirements for an end-to-end software application to be tested, the structured BPM file including a plurality of flow objects and linking objects, and wherein the generating further comprises mapping each of one or more identified elements from the generated structured BPM file to a corresponding location in a node structure utilizing at least attribute information associated with each of the one or more identified elements, wherein a unique ID-key value is assigned to each of the one or more identified elements that maps the identified element with its corresponding location in the node structure;
validating, by the application testing computing device, the generated structured BPM file in association with one or more validation rules;
generating, by the application testing computing device, a graphical representation of data in the validated structured BPM file, wherein the graphical representation comprises a functional flow layout representative of a node structure embodying all possible scenarios to be handled by the software application in the validated structured BPM file;
identifying, by the application testing computing device, a plurality of data paths from the generated functional flow layout in the graphical representation, wherein each of the plurality of data paths are associated with one or more corresponding scenarios of the possible scenarios;
generating, by the application testing computing device, one or more test cases associated with the functioning of the end-to-end software application for each identified plurality of data paths based on a role performed by the identified data paths and an associated decomposed task-flow for the set of business requirements for the end-to-end software application, wherein each of the generated one or more test cases comprises a test step description describing a task required to be performed;
applying, by the application testing computing device, the one or more generated test cases to a corresponding data path in the end-to-end software application;
comparing, by the application testing computing device, an actual outcome from the data path of the software application to an expected outcome for the data path; and
generating, by the application testing computing device, a report including at least the actual outcome and the expected outcome, wherein the generated report is displayable on a computing device screen.

2. The method of claim 1 , further comprising storing by the application testing computing device, information associated with at least the generated structured BPM file in a memory, wherein the stored information is mapped to an established test case profile for the end-to-end software application being tested.

3. The method of claim 1 , wherein generating the structured BPM file further comprises:
parsing by the application testing computing device, the generated structured BPM file to identify all of the one or more elements included in the structured BPM file;
creating by the application testing computing device, a node structure including a plurality of nodes; and
determining by the application testing computing device, one or more relationships between the one or more identified elements with respect to the node structure.

4. The method of claim 1 , wherein the generating of one or more test cases further comprises:
identifying by the application testing computing device, a role of a selected data path of the structured BPM file;
identifying by the application testing computing device, test conditions for the selected data path by analyzing branch elements to recognize required conditional information for user input for the data path; and
determining by the application testing computing device, for each generated test case for the selected data path, an expected outcome for each branch element based on the user input and storing the expected outcome for a test case profile in a memory.

5. The method of claim 1 , further comprising performing a test case regression technique prior to the validation step, the method including:
determining by the application testing computing device, if the structured BPM file is an updated version of a previous version of a structured BPM file;
extracting by the application testing computing device, flow objects from the updated version of the structured BPM file and comparing the extracted flow objects with corresponding flow objects in the previous version;
identifying by the application testing computing device, one or more flow objects in the updated version that have changed with respect to the previous version; and
identifying by the application testing computing device, affected flow paths of the changed flow objects in the updated version, wherein the changed flow objects and identified affected flow paths are to be validated in the validation step.

6. The method of claim 1 , wherein at least one possible scenario further comprises a sequence of executable activities to be performed by the software application.

7. The method of claim 1 , wherein at least one possible scenario further comprises one or more states and transitions associated with a sequence of executable activities to be performed by the software application.

8. The method as set forth in claim 1 , wherein the generated graphical representation of data in the validated structured BPM file is a hierarchical structure.

9. A non-transitory machine readable medium having stored thereon instructions for testing an end-to-end software application having a plurality of functionalities, comprising machine executable code which when executed by at least one processor of a computing device, causes the processor to:
generate a structured business process model (BPM) file representative of a set of business requirements for an end-to-end software application to be tested, the structured BPM file including a plurality of flow objects and linking objects, and wherein the generating further comprises map each of one or more identified elements from the generated structured BPM file to a corresponding location in a node structure utilizing at least attribute information associated with each of the one or more identified elements, wherein a unique ID-key value is assigned to each of the one or more identified elements that maps the identified element with its corresponding location in the node structure;
validate the generated structured BPM file in association with one or more validation rules;
generate a graphical representation of data in the validated structured BPM file, wherein the graphical representation comprises a functional flow layout representative of a node structure embodying all possible scenarios to be handled by the software application in the validated structured BPM file;
identify a plurality of data paths from the generated functional flow layout in the graphical representation, wherein each of the plurality of data paths are associated with one or more corresponding scenarios of the possible scenarios;
generate one or more test cases associated with the functioning of the end-to-end software application for each identified plurality of data paths based on a role performed by the identified data paths and an associated decomposed task-flow for the set of business requirements for the end-to-end software application, wherein each of the generated one or more test cases comprises a test step description describing a task required to be performed;
apply the one or more

Assignees

• Infosys Ltd

Inventors

• Pasala Anjaneyulu
• Dsouza Sharal Nisha

Classifications

• G06Q10/067

  Enterprise or organisation modelling · CPC title

• G06F11/3684 Primary

  for test design, e.g. generating new test cases · CPC title

• G06F8/10

  Requirements analysis; Specification techniques · CPC title

• G06F8/35

  model driven · CPC title

• G06Q10/0633

  Workflow analysis · CPC title