Agile unit and regression testing framework for domain specific languages

• US 9,032,361 B2
• Filed: 06/12/2012
• Issued: 05/12/2015
• Est. Priority Date: 12/15/2011
• Status: Active Grant

• Current Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Original Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Inventors: Dhalait, ShamimAhmad Dadamir
• Primary Examiner(s): DENG, ANNA CHEN
• Application Number:
  US13/494,256
• Publication Number:
  US 20130159963A1
• Time in Patent Office: 1,064 Days
• Field of Search: 717/104
• US Class Current: 717/104
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases

Abstract

According to one aspect of the invention, a system and method for unit and regression testing has been developed. The system is capable to automate unit/regression test case preparation, remote execution, provide XML based assert mechanism to evaluate test results, maintenance and versioning. The present system enables model driven testing of domain specific languages and provides a user friendly mechanism to perform Unit and Regression Testing.

Claims

1. A method of unit and regression testing for model aware domain specific languages, the method comprising a processor implemented steps of:

modeling an operation present in a repository for a test driven development process, the operation comprising a specification of designing requirements for testing to generate an application library code;

generating a blank operation template from the application library code thereof corresponding to the operation, the blank operation template comprising an input XML and an expected output XML thereof, wherein the input XML refers to a set of test cases, and the expected output XML refers to results that are expected post running of the set of the test cases;

building an executable unit test load to integrate business logic therein by using predefined unit test stubs and system libraries;

executing the unit test load and comparing a resulting actual output XML with the expected output XML to determine states of the set of the test cases, wherein a state of a test case refers to either pass state or fail state;

identifying defects unveiled during the comparison; and

versioning the test cases for the future reusability by selecting valid test cases with the pass states, wherein the valid test cases are used to build regression test suites, wherein the regression test are used for performing regression testing, wherein regression testing comprises executing an entirety of the regression test suites to uncover unknown defects to all parts of an enterprise computer application due to a change at a unit level of the enterprise computer application.

2. The method of claim 1, wherein the operation refers to a unit testing module.

3. The method of claim 1, wherein the repository consists of artifacts but not limited to input XML files, expected output XML files, regression test suite metadata and the like.

4. The method of claim 1, wherein the application library code provides functionalities of sophisticated memory management and object oriented view of database.

5. The method of claim 1, wherein the blank operation template refers to a template generated by MasterCraft.

6. The method of claim 1, wherein the unit test load comprises of dependent components of drive modules, object binaries and application code library.

7. The method of claim 1, wherein the blank operation template further comprises an empty operation shell, wherein the business logic is encoded in model aware domain specific language with the empty operation shell using an eclipse plug-in, wherein the eclipse plug-in uses the predefined unit test stubs and system libraries.

8. A computerized system of unit and regression testing for domain specific languages, the system having at least a memory storing a plurality of modules and a processor for executing code of plurality of modules, the plurality of modules of the system comprising:

an input module, stored in the memory, configured to generate an input XML and an expected output XML, wherein the input XML refers to a set of input test cases, and the expected output XML refers to results that are expected post running of the set of the test cases;

a modeling unit, stored in the memory, adapted to accept input from a repository and generate an operation for testing in a test driven development process;

a code generating module, stored in the memory, coupled with the repository and is configured to generate domain specific language code templates and an application library code for operations accessed from the repository;

an executing module, stored in the memory, configured to invoke a function that reads the input XML and call an unit test load to write output to an output file;

a comparing module, stored in the memory, adapted to compare a resulting actual output XML with the expected output XML, assign a flag to each compared test case in the set of test cases to indicate a state of the each compared test case in the set of the test cases, wherein the state of the each compared test case refers to either pass state or fail state; and

a result generating module, stored in the memory, adapted to report defects unveiled during comparison, wherein the test cases with pass state are used to build regression test suites, wherein the regression test suites are used for performing regression testing, wherein regression testing comprises executing an entirety of the regression test suites to uncover unknown defects to all parts of an enterprise computer application due to a change at a unit level of the enterprise computer application.

9. The system of claim 8, wherein the function refers to Job Control Language.

10. The system of claim 8, wherein the output file refers to the output file generated post execution of the test procedures.

11. The system of claim 8, wherein the operation refers to a unit testing module.

12. The system of claim 8, wherein the repository consists of artifacts including but not limited to input XML files, expected output XML files, regression test suite metadata and the like.

13. The system of claim 8, wherein the application library code provides functionalities of sophisticated memory management and object oriented view of database.

14. The system of claim 8, wherein the blank operation template refers to a template generated by MasterCraft.

15. The system of claim 8, wherein the unit test load comprises of dependent components of drive modules, object binaries and application code library.