We claim:
1. A computer implemented method for automating unit test case generation for one or more methods associated with an application source code, wherein the method is implemented by a processor executing program instructions stored in a memory, the method comprising:
identifying, by the processor, one or more potential executable paths associated with a selected method by analysing a code base extract using a path solving technique;
identifying, by the processor, one or more calls to external dependencies associated with each of the one or more potential executable paths using a symbolic execution technique;
generating, by the processor, one or more hints for the identified one or more calls to external dependencies, wherein each hint is representative of call information associated with the external dependencies;
updating, by the processor, the one or more hints with accurate implementations of an object type in each of the one or more hints, wherein the accurate implementation of each object type is identified based on determination of a predefined category associated with the object type;
updating, by the processor, each of the one or more hints with respective ideal return value, wherein the ideal return value of each of the one or more calls to external dependencies is determined based on an aggregated conditional expression associated with respective paths using one or more constraint solving techniques; and
generating, by the processor, a unit test code for the selected method by processing the one or more hints with a test data and an exclusion list.

2. The method as claimed in claim 1, wherein the codebase extract is generated by analysing and parsing the application source code, further wherein the codebase extract includes a class dependency graph and one or more abstract syntax graphs associated with the application source code.
3. The method as claimed in claim 1, wherein the code base extract is analysed for identifying one or more potential executable paths on receiving a request for generation of unit test for the selected method.
4. The method as claimed in claim 1, wherein identifying one or more calls to external dependencies comprises executing one or more statements associated with each of the one or more potential paths using a symbolic execution technique; creating and updating a symbol table while interpreting each statement associated with the respective one or more paths; and identifying a statement interpreted as method invocation as a call to external dependency.
5. The method as claimed in claim 4, wherein the hint is generated as a by-product of execution of the statement interpreted as external dependency.
6. The method as claimed in claim 1, wherein the one or more calls to external dependencies include calls to other methods in the application source code, calls to external libraries, database queries and calls to web service.
7. The method as claimed in claim 4, wherein the symbol table is a customized data structure configured to store semantic information associated with an expression, variables present in the expression, and the one or more methods associated with application source code.
8. The method as claimed in claim 7, wherein the semantic information includes scope, variable name,

variable data type, associated symbol, value, format of the value, constraints, variable type, object type information, resolved data type of the variable, type cast information associated with the object, expression information.
9. The method as claimed in claim 1, wherein one or more conditional expressions associated with each of the one or more potential executable paths are collected and aggregated.
10. The method as claimed in claim 1, wherein the call information associated with the external dependency includes object type, method being called, return type, arguments with values and associated symbols.
11. The method as claimed in claim 1, wherein a format of the one or more hints is selected from xml and JSON.
12. The method as claimed in claim 1, wherein the predefined categories associated with the object type include an interface, an abstract class and a base class.
13. The method as claimed in claim in 12, wherein the accurate implementation for the object type is identified using type cast information associated with the object from the symbol table if the object type is associated with the base class.
14. The method as claimed in claim in 12, wherein the accurate implementation for the object type is identified using a predefined-list of possible implementations along with a reflection technique, if the object type is associated with an interface or an abstract class.
15. The method as claimed in claim 1, wherein each ideal return value is representative of a value which is to be returned by respective external call such that downstream execution of respective path is feasible.

16. The method as claimed in claim 1, wherein the exclusion list comprises a pre-generated list of object types which are not to be mocked.
17. The method as claimed in claim 1, wherein processing of the one or more hints with the exclusion list comprises determining if the object type associated with one or more hints is associated with the exclusion list.
18. A system for automating unit test case generation for one or more methods associated with an application source code, wherein the system interfaces with an application subsystem comprising the application source code, the system comprising:
a memory storing program instructions; a processor configured to execute program instructions stored in the memory; and a unit test generation engine in communication with the processor configured to:
identify one or more potential executable paths associated with a selected method by analysing a code base extract using a path solving technique;
identify one or more calls to external dependencies associated with each of the one or more potential executable paths using a symbolic execution technique;
generate one or more hints for the identified one or
more calls to external dependencies, wherein each hint is
representative of call information associated with the
external dependencies;
update one or more hints with respective accurate implementations of an object type in each of the one or more hints, wherein the accurate implementation of each object type is identified based on determination of a predefined category associated with the object type;

update each of the one or more hints with respective ideal return value, wherein the ideal return value of each of the one or more calls to external dependencies is determined based on an aggregated conditional expression associated with respective paths using one or more constraint solving techniques; and
generate a unit test code for the selected method by processing the one or more hints with a test data and an exclusion list.
19. The system as claimed in claim 18, wherein the unit test generation engine comprises a code extraction unit in communication with the processor, the code extraction unit configured to generate a codebase extract by analysing the application source code using static analysis and parsing the analysed application source code, further wherein the codebase extract includes a class dependency graph and one or more abstract syntax graphs associated with the application source code.
20. The system as claimed in claim 18, wherein the unit test generation engine comprises a computation engine in communication with the processor, the computation engine comprises a path solving unit configured to: analyse the codebase extract on receiving a request for generation of unit test for the selected method; identify one or more potential executable paths within the selected method using a path solving technique; and filter invalid or infeasible paths before transmitting for further processing.
21. The system as claimed in claim 20, wherein the computation engine comprises a hint generation unit configured to: execute one or more statements associated with each of the one or more potential paths using a symbolic execution technique; create and update a symbol table while interpreting each statement associated with respective one or more paths; and identify a statement

interpreted as method invocation as a call to external dependency.
22. The system as claimed in claim 21, wherein the hint generation unit is configured to collect one or more conditional expressions associated with each of the one or more paths; and aggregate the one or more conditional expressions associated with each path respectively.
23. The system as claimed in claim 21, wherein the hint is generated as a by-product of execution of the statement interpreted as external dependency.
24. The system as claimed in claim 18, wherein the one or more calls to external dependencies include calls to other methods associated with the application source code, calls to external libraries, database queries and calls to web service.
25. The system as claimed in claim 21, wherein the symbol table is a customized data structure configured to store semantic information associated with an expression, variables present in the expression, and the one or more methods associated with application source code.
26. The system as claimed in claim 25, wherein the semantic information includes scope, variable name, variable data type, associated symbol, value, format of the value, constraints, variable type including literal, number, null or list, object type information, resolved data type of the variable, type cast information associated with the object, expression information.
27. The system as claimed in claim 18, wherein the call information associated with the external dependency includes object type, method being called, return type, arguments with values and associated symbols.
28. The system as claimed in claim 18, wherein a format of the one or more hints is selected from xml and JSON.

29. The system as claimed in claim 18, wherein the predefined categories associated with the object type include an interface, an abstract class and a base class.
30. The system as claimed in claim 29, wherein the accurate implementation for the object type is identified using type cast information associated with the object from the symbol table if the object type is associated with the base class.
31. The system as claimed in claim 29, wherein the accurate implementation for the object type is identified using a predefined-list of possible implementations along with a reflection technique, if the object type is associated with an interface or an abstract class.
32. The system as claimed in claim 18, wherein each ideal return value is representative of a value which is to be returned by respective external call such that downstream execution of the respective path is feasible.
33. The system as claimed in claim 18, wherein the exclusion list comprises a pre-generated list of object types which are not to be mocked.
34. The system as claimed in claim 18, wherein the unit test generation engine comprises a code generation unit in communication with the processor, the code generation unit configured to: determine if the object type associated with respective hints are included in the exclusion list; create appropriate mock statement, if the object type is not found in the exclusion list; and generate the unit test case for the selected method by processing the one or more hints with test data and the exclusion list.
35. A computer program product comprising:
a non-transitory computer-readable medium having computer-readable program code stored thereon, the

computer-readable program code comprising instructions that, when executed by a processor, cause the processor to:
identify one or more potential executable paths associated with a selected method by analysing a code base extract using a path solving technique;
identify one or more calls to external dependencies associated with each of the one or more potential executable paths using a symbolic execution technique;
generate one or more hints for the identified one or
more calls to external dependencies, wherein each hint is
representative of call information associated with the
external dependencies;
update one or more hints with accurate implementations of an object type in each of the one or more hints, wherein the accurate implementation of each object type is identified based on determination of a predefined category associated with the object type;
update each of the one or more hints with respective ideal return value, wherein the ideal return value of each of the one or more calls to external dependencies is determined based on an aggregated conditional expression associated with respective paths using one or more constraint solving techniques; and
generate a unit test code for the selected method by processing the one or more hints with a test data and an exclusion list.