Claims:We Claim:

1. A method of performing unit testing, the method comprising:
generating, by a testing system (102), a source code (212) based on a compiled code (101) received from a user;
classifying, by the testing system (102), the source code (212) into testable components and non-testable components, wherein the testable components comprise units of source code;
identifying, by the testing system (102), one or more rules from a set of organized rules (214) based on the units of source code;
determining, by the testing system (102), one or more expected parameters (216) corresponding to a unit of source code based on the one or more rules and content of the unit of source code, wherein the content comprises one or more input fields;
generating, by the testing system (102), one or more test cases (103), (218) for each of the one or more input fields of the unit of source code by using the one or more expected parameters (216); and
performing, by the testing system (102), a script-less unit testing of the compiled code (101) by executing the one or more test cases (103), (218).

2. The method as claimed in claim 1, wherein the compiled code (101) comprises at least one of an executable code and any compiled code associated with a programming language.

3. The method as claimed in claim 1, wherein the units of source code comprises at least one of a subroutine, a procedure, a function, a method, a callable unit, or a subprogram associated with the compiled code (101).

4. The method as claimed in claim 1, wherein the one or more test cases (103), (218) are associated with at least one of a positive test case and a negative test case.

5. The method as claimed in claim 1 further comprising receiving values corresponding to the one or more expected parameters (216) and one or more testing parameters from the user through a user-interface.

6. The method as claimed in claim 1 further comprising dynamically updating a newly added unit of source code into the testable components.

7. A testing system (102) for performing unit testing, the system (102) comprising:
a processor (204); and
a memory (206) communicatively coupled to the processor (204), wherein the memory (206) stores processor-executable instructions, which, on execution, causes the processor (204) to:
generate a source code (212) based on a compiled code (101) received from a user;
classify the source code (212) into testable components and non-testable components, wherein the testable components comprise units of source code;
identify one or more rules from a set of organized rules (214) based on the units of source code;
determine one or more expected parameters (216) corresponding to a unit of source code based on the one or more rules and content of the unit of source code, wherein the content comprises one or more input fields;
generate one or more test cases (103), (218) for each of the one or more input fields of the unit of source code by using the one or more expected parameters (216); and
perform a script-less unit testing of the compiled code (101) by executing the one or more test cases (103), (218).

8. The testing system (102) as claimed in claim 7, wherein the compiled code (101) comprises at least one of an executable code and any compiled code associated with a programming language.

9. The testing system (102) as claimed in claim 7, wherein the units of source code comprises at least one of a subroutine, a procedure, a function, a method, a callable unit, and a subprogram associated with the compiled code (101).

10. The testing system (102) as claimed in claim 7, wherein the one or more test cases (103), (218) are associated with at least one of a positive test case and a negative test case.

11. The testing system (102) as claimed in claim 7, wherein the processor (204) is further configured to receive values corresponding to the one or more expected parameters (216) and one or more testing parameters from the user through a user-interface.

12. The testing system (102) as claimed in claim 7, wherein the processor (204) is further configured to dynamically update a newly added unit of source code into the testable components.

Dated this 8th day of February 2017

Swetha SN
Of K&S Partners
Agent for the Applicant , Description:TECHNICAL FIELD

The present disclosure relates in general to software testing. More particularly, but not exclusively, the present disclosure discloses a method and system for performing script-less unit testing.