Abstract: The present subject matter relates to end to end automated testing of software applications. In one embodiment, a computer implemented method comprises obtaining, by a process modeling module (112), a process workflow diagram (150) as an input. The process workflow diagram (150) is indicative of transfer of data and tasks through a work process for a service. The method may further include creating, by a test scenario generation module (114), a plurality of test scenarios (134) based on the process workflow diagram (150). Further, the method may include generating, by a test script generation module (118), a plurality of test scripts (136) from the plurality of test scenarios (134). The method may also include executing, by a script execution module (120), at least one of the plurality of test scripts (136) on the software application to generate test results (138).
DESC:END TO END AUTOMATED TESTING OF A SOFTWARE APPLICATION ,CLAIMS:1. A computer implemented method for end to end automated testing of a software application, the method comprising:
obtaining, by a process modeling module (112), a process workflow diagram (150) as an input, wherein the process workflow diagram (150) is indicative of transfer of data and tasks through a work process for a service;
creating, by a test scenario generation module (114), a plurality of test scenarios (134) based on the process workflow diagram (150);
generating, by a test script generation module (118), a plurality of test scripts (136) based on the plurality of test scenarios (134); and
executing, by a script execution module (120), at least one of the plurality of test scripts (136) on the software application to generate test results (138).
2. The method as claimed in claim 1, wherein the obtaining comprises generating an Extensible Markup Language (XML) Process Definition Language (XPDL) file from the process workflow diagram (150).
3. The method as claimed in claim 1, wherein the creating comprises determining a plurality of paths in the process workflow diagram (150), and wherein each of the plurality of paths corresponds to each of the plurality of test scenarios (134).
4. The method as claimed in claim 1, wherein the creating further comprises uploading, by the test scenario generation module (114), the plurality of test scenarios (134) in a database (126).
5. The method as claimed in claim 1, wherein the generating comprises retrieving, by the test script generation module (118), the plurality of test scenarios (134) from the database (126).
6. The method as claimed in claim 1, wherein the generating further comprises uploading, by the test script generator module (118), the plurality of test scripts (136) in the database (126).
7. An automation system (100) comprising:
a processor (102);
a test scenario generation module (114), coupled to the processor (102), to,
receive a process workflow diagram (150) as an input, wherein the process workflow diagram (150) is indicative of transfer of data and tasks through a work process for a service;
determine a plurality of paths in the process flow diagram (150); and
create a plurality of test scenarios (134) based on the plurality of paths;
a test script generation module (118), coupled to the processor (102), to,
generate a plurality of test scripts (136) from the plurality of test scenarios (134); and
automatically update the plurality of test scripts (136) in a database (126); and
a script execution module (120), coupled to the processor (102), to execute at least one of the plurality of test scripts (136) on an application under test (AUT) to obtain test results (138), wherein the test results (138) are stored in the database (126).
8. The automation system (100) as claimed in claim 7 further comprising a process modeling module (112), coupled to the processor (102), to generate an Extensible Markup Language (XML) Process Definition Language (XPDL) file from the process workflow diagram (150).
9. The automation system (100) as claimed in claim 7 further comprising a test management module (116), coupled to the processor (102), to invoke the test script generation module (118) to convert the plurality of test scenarios (134) into a plurality of test scripts (136);
10. The automation system (100) as claimed in claim 7 further comprising a test data generation module (122), coupled to the processor (102), to share data with the script execution module (120), for execution of the at least one of the plurality of test scripts (136) on an application under test (AUT).
11. A computer readable medium having embodied thereon a computer program for executing a method for end to end automated testing of a software application, the method comprising:
obtaining, by a process modeling module (112), a process workflow diagram (150) as an input, wherein the process workflow diagram (150) is indicative of transfer of data and tasks through a work process for a service;
creating, by a test scenario generation module (114), a plurality of test scenarios (134) based on the process workflow diagram (150);
generating, by a test script generation module (118), a plurality of test scripts (136) based on the plurality of test scenarios (134); and
executing, by a script execution module (120), at least one of the plurality of test scripts (136) on the software application to generate test results (138).
| Section | Controller | Decision Date |
|---|---|---|
| 15 | Dilip Dandotiya | 2023-07-06 |
| 15, 11B(4) | Dilip Dandotiya | 2023-07-21 |
| # | Name | Date |
|---|---|---|
| 1 | 1809-MUM-2012-RELEVANT DOCUMENTS [20-07-2023(online)].pdf | 2023-07-20 |
| 1 | Form-2(Online).pdf | 2018-08-11 |
| 2 | 1809-MUM-2012-US(14)-HearingNotice-(HearingDate-21-07-2023).pdf | 2023-07-06 |
| 2 | Drawings.pdf | 2018-08-11 |
| 3 | 1809-MUM-2012-Response to office action [15-02-2023(online)].pdf | 2023-02-15 |
| 3 | 1809-MUM-2012-POWER OF ATTORNEY(14-8-2012).pdf | 2018-08-11 |
| 4 | 1809-MUM-2012-PETITION UNDER RULE 137 [13-02-2023(online)].pdf | 2023-02-13 |
| 4 | 1809-MUM-2012-FORM 5(2-7-2014).pdf | 2018-08-11 |
| 5 | 1809-MUM-2012-Proof of Right [13-02-2023(online)].pdf | 2023-02-13 |
| 5 | 1809-MUM-2012-CORRESPONDENCE(2-7-2014).pdf | 2018-08-11 |
| 6 | 1809-MUM-2012-Written submissions and relevant documents [13-02-2023(online)].pdf | 2023-02-13 |
| 6 | 1809-MUM-2012-CORRESPONDENCE(14-8-2012).pdf | 2018-08-11 |
| 7 | 1809-MUM-2012-FORM-26 [31-01-2023(online)].pdf | 2023-01-31 |
| 7 | 1809-MUM-2012-FORM 3.pdf | 2019-06-13 |
| 8 | 1809-MUM-2012-FORM-26 [24-01-2023(online)].pdf | 2023-01-24 |
| 8 | 1809-MUM-2012-FORM 2.pdf | 2019-06-13 |
| 9 | 1809-MUM-2012-Correspondence to notify the Controller [16-01-2023(online)].pdf | 2023-01-16 |
| 9 | 1809-MUM-2012-FORM 18.pdf | 2019-06-13 |
| 10 | 1809-MUM-2012-FER.pdf | 2019-07-18 |
| 10 | 1809-MUM-2012-US(14)-HearingNotice-(HearingDate-30-01-2023).pdf | 2023-01-11 |
| 11 | 1809-MUM-2012-CLAIMS [17-01-2020(online)].pdf | 2020-01-17 |
| 11 | 1809-MUM-2012-PETITION UNDER RULE 137 [17-01-2020(online)].pdf | 2020-01-17 |
| 12 | 1809-MUM-2012-COMPLETE SPECIFICATION [17-01-2020(online)].pdf | 2020-01-17 |
| 12 | 1809-MUM-2012-OTHERS [17-01-2020(online)].pdf | 2020-01-17 |
| 13 | 1809-MUM-2012-DRAWING [17-01-2020(online)].pdf | 2020-01-17 |
| 13 | 1809-MUM-2012-FER_SER_REPLY [17-01-2020(online)].pdf | 2020-01-17 |
| 14 | 1809-MUM-2012-DRAWING [17-01-2020(online)].pdf | 2020-01-17 |
| 14 | 1809-MUM-2012-FER_SER_REPLY [17-01-2020(online)].pdf | 2020-01-17 |
| 15 | 1809-MUM-2012-COMPLETE SPECIFICATION [17-01-2020(online)].pdf | 2020-01-17 |
| 15 | 1809-MUM-2012-OTHERS [17-01-2020(online)].pdf | 2020-01-17 |
| 16 | 1809-MUM-2012-CLAIMS [17-01-2020(online)].pdf | 2020-01-17 |
| 16 | 1809-MUM-2012-PETITION UNDER RULE 137 [17-01-2020(online)].pdf | 2020-01-17 |
| 17 | 1809-MUM-2012-US(14)-HearingNotice-(HearingDate-30-01-2023).pdf | 2023-01-11 |
| 17 | 1809-MUM-2012-FER.pdf | 2019-07-18 |
| 18 | 1809-MUM-2012-Correspondence to notify the Controller [16-01-2023(online)].pdf | 2023-01-16 |
| 18 | 1809-MUM-2012-FORM 18.pdf | 2019-06-13 |
| 19 | 1809-MUM-2012-FORM 2.pdf | 2019-06-13 |
| 19 | 1809-MUM-2012-FORM-26 [24-01-2023(online)].pdf | 2023-01-24 |
| 20 | 1809-MUM-2012-FORM 3.pdf | 2019-06-13 |
| 20 | 1809-MUM-2012-FORM-26 [31-01-2023(online)].pdf | 2023-01-31 |
| 21 | 1809-MUM-2012-CORRESPONDENCE(14-8-2012).pdf | 2018-08-11 |
| 21 | 1809-MUM-2012-Written submissions and relevant documents [13-02-2023(online)].pdf | 2023-02-13 |
| 22 | 1809-MUM-2012-CORRESPONDENCE(2-7-2014).pdf | 2018-08-11 |
| 22 | 1809-MUM-2012-Proof of Right [13-02-2023(online)].pdf | 2023-02-13 |
| 23 | 1809-MUM-2012-FORM 5(2-7-2014).pdf | 2018-08-11 |
| 23 | 1809-MUM-2012-PETITION UNDER RULE 137 [13-02-2023(online)].pdf | 2023-02-13 |
| 24 | 1809-MUM-2012-POWER OF ATTORNEY(14-8-2012).pdf | 2018-08-11 |
| 24 | 1809-MUM-2012-Response to office action [15-02-2023(online)].pdf | 2023-02-15 |
| 25 | Drawings.pdf | 2018-08-11 |
| 25 | 1809-MUM-2012-US(14)-HearingNotice-(HearingDate-21-07-2023).pdf | 2023-07-06 |
| 26 | Form-2(Online).pdf | 2018-08-11 |
| 26 | 1809-MUM-2012-RELEVANT DOCUMENTS [20-07-2023(online)].pdf | 2023-07-20 |
| 1 | 1809MUM2012_18-07-2019.pdf |