Claims:We Claim:
1. A method of enabling self-maintainable test automation by a test automation system, said method comprising:
receiving, by the test automation system, one or more input test scenarios associated with one or more applications executing in a real time environment;
comparing, by the test automation system, the one or more input test scenarios with one or more corresponding historical test scenarios to identify one or more functional changes associated with the one or more input test scenarios;
determining, by the test automation system, one or more reusable automation units of the one or more input test scenarios based on the comparison;
determining, by the test automation system, one or more test data units corresponding to the one or more reusable automation units thus determined; and
updating, by the test automation system, the one or more reusable automation units and the one or more test data units based on the one or more functional changes thus identified.

2. The method as claimed in claim 1, wherein determining the one or more reusable automation units comprising the step of determining one or more common user actions associated with both the one or more input test scenarios and the one or more historical test scenarios.

3. The method as claimed in claim 1, wherein determining the one or more test data units corresponding to the one or more reusable automation units comprising the step of determining one or more common test data associated with both the one or more input test scenarios and the one or more historical test scenarios.

4. The method as claimed in claim 1, further comprising:
receiving one or more training test scenarios associated with one or more applications executed in a test environment coupled with a test automation repository;
creating a test automation suite for the one or more training test scenarios, wherein the test automation suite comprising the one or more reusable automation units and the one or more test data units associated with the one or more training test scenarios; and
storing the test automation suite and the one or more training test scenarios as the one or more historical test scenarios in the test automation repository.

5. The method as claimed in claim 4, wherein the step of creating the test automation suite comprising the steps of:
deriving the one or more user actions corresponding to the one or more training test scenarios received based on the execution of the one or more applications;
grouping the one or more user actions into one or more automated system actions based on logical similarity among the one or more user actions thus derived;
determining the one or more reusable automation units based on the grouping of the one or more automated system actions;
determining the one or more test data units corresponding to the one or more reusable automation units thus determined; and
creating the test automation suite comprising the one or more reusable automation units and the one or more test data units.

6. The method as claimed in claim 1, further comprising:
receiving the one or more actions associated with the one or more input test scenarios;
determining one or more objects based on which the one or more actions are performed;
determining one or more object information comprising at least location and one or more properties associated with the one or more objects; and
updating the one or more determined object information with the one or more functional changes thus identified with the one or more input test scenarios.

7. A system for enabling self-maintainable test automation, said system comprises:
a processor;
a test automation repository coupled with the processor and configured to store a test automation suite and one or more historical test scenarios; and
a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
receive one or more input test scenarios associated with one or more applications executing in a real time environment;
compare the one or more input test scenarios with the one or more corresponding historical test scenarios to identify one or more functional changes associated with the one or more input test scenarios;
determine one or more reusable automation units of the one or more input test scenarios based on the comparison;
determine one or more test data units corresponding to the one or more reusable automation units thus determined; and
update the one or more reusable automation units and the one or more test data units based on the one or more functional changes thus identified.

8. The system as claimed in claim 7, wherein the processor is configured to determine the one or more reusable automation units by performing the step of determining one or more common user actions associated with both the one or more input test scenarios and the one or more historical test scenarios.

9. The system as claimed in claim 7, wherein the processor is configured to determine the one or more test data units corresponding to the one or more reusable automation units by performing the step of determining one or more common test data associated with both the one or more input test scenarios and the one or more historical test scenarios.

10. The system as claimed in claim 7, wherein the processor is further configured to perform the steps of:
receiving one or more training test scenarios associated with one or more applications executed in a test environment coupled with a test automation repository;
creating a test automation suite for the one or more training test scenarios, wherein the test automation suite comprising the one or more reusable automation units and the one or more test data units associated with the one or more training test scenarios; and
storing the test automation suite and the one or more training test scenarios as the one or more historical test scenarios in the test automation repository.

11. The system as claimed in claim 10, wherein the processor is configured to create the test automation suite by performing the steps of:
deriving the one or more user actions corresponding to the one or more training test scenarios received based on the execution of the one or more applications;
grouping the one or more derived user actions into one or more automated system actions based on logical similarity among the one or more user actions thus derived;
determining the one or more reusable automation units based on the grouping of the one or more automated system actions;
determining the one or more test data units corresponding to the one or more reusable automation units thus determined; and
creating the test automation suite comprising the one or more reusable automation units and the one or more test data units.

12. The system as claimed in claim 7, wherein the processor is further configured to perform one or more steps comprising:
receiving the one or more actions associated with the one or more input test scenarios;
determining one or more objects based on which the one or more actions are performed;
determining one or more object information comprising at least location and one or more properties associated with the one or more objects; and
updating the one or more determined object information with the one or more functional changes thus identified with the one or more input test scenarios.

Dated this 11th day of March, 2016

Swetha SN
Of K&S Partners
Agent for the Applicant
, Description:FIELD OF THE DISCLOSURE
The present subject matter is related, in general to automated testing of computer applications, and more particularly, but not exclusively to a method and a system for enabling self-maintainable test automation.