METHOD AND SYSTEM FOR GENERATING ONE OR MORE MODELS FROM EXISTING
TEST CASES FOR A DEVICE
FIELD
The present disclosure generally relates to a method and system for representing a device using its test case information. More particularly, it concerns a method and system for generating one or more models representing a device from existing test cases.
BACKGROUND
Presently, test cases pertaining to a system are maintained as plain English in various formats. However such textual representation of data is not direct or easy to assimilate. Highly skilled resources are required to understand the system and a lot of time needs to be invested to create the models manually using any available (UML) modeling tool.
Usually models give a better picture of the steps involved and process flow of the solution to any human mind. Research says that is faster for a human mind to grasp a process flow shown using a model rather than text
US7076713 describes a Test Generator for Converting a Model of Computer Component Object Behavior and Stimulus Values to Test Script'. This document relates to an apparatus and an associated method that tests the response of a computer component. The apparatus includes a modeler, a tester, and a test generator. The modeler provides a model of the computer component object behavior. The tester provides stimulus values to be applied to the computer component object. The test generator converts the mode! of the computer component object behavior and the stimulus values into test script. However, in this document,

a model of computer component object behavior and stimulus values are converted to test script, where as the present disclosure generates a mode! from the given manual test cases of a computer component object in a specified excel format.
US 2007/0094541 Al describes a 'Method and Apparatus for Generating Test Execution Sequences Automatically for a Software Testing Process'. This document provides a method for generating test execution sequences automatically for a software testing process. A method in accordance with an embodiment of the present invention includes: inputting scripts of test cases; generating test execution sequences based on the scripts; and selecting valid test execution sequences according to pre-determined criteria to generate final test execution sequences. With this invention, test execution sequences with a plurality of test cases may be generated automatically, so as to improve the ability of finding bugs in a software application being tested in automatic software testing. However, in this document, optimized test execution sequences can be generated automatically so as to improve the ability of finding bugs in a software application being tested in automatic software testing, whereas in the present disclosure, models are generated from the given manual test cases of a computer component object in a specified excel format.
Thus, there is a requirement for an alternate approach as opposed to the current system of manual creation of models. There is a need for a system that can generate models in an automated manner from manual test cases maintained for a device under test. Models give a better and quicker picture of the process flow to any tester or user. Also these models can be used for automation, if any automation engine is been implemented in the testing cycle.
SUMMARY
In order to obviate the above drawbacks the instant invention provides a method and system for generating one or more models representing a device from existing test cases.

The present disclosure relates to testing and validation activity being done either on software applications or devices with embedded software. It saves a huge amount of time, effort and cost incurred in the creation of models.
To achieve the aforesaid and other objectives related to efficient testing, the instant invention provides a method for generating one or more models from existing test cases for a device, comprising the steps of obtaining one or more test variables and their values for one or more test cases, analyzing each test case with the corresponding test variable values, capturing each component involved in the analysis of the test case and each other component it communicates with along with their attributes and states, assimilating transitions for each component between states, interactions between and the conditions and/or attributes for each such interaction, and forming one or more models by depicting each component and linking it with each other state it transitions into.
It also provides a system for generating a model from test case information for a device comprising of receiver configured to obtain one or more test variables and their values for one or more test cases, analyzer coupled to the receiver and configured to analyze each test case with the corresponding test variable values, component builder coupled to the analyzer and configured to capture each component involved in the analysis and each other component it communicates with, and model builder coupled to the component builder and configured to form a model by depicting each component and linking it with each other component it communicates with
BRIEF DESCRIPTION OF THE DRAWINGS
The detailed description is described with reference to the accompanying figures.

FIGURE 1 depicts the primary embodiment of the method described in the disclosure;
FIGURE 2 depicts the primary embodiment of the system described in the disclosure; and
FIGURES 3A and 3B depict an example of the manual test case data and corresponding model created using the technology described in this disclosure
DETAILED DESCRIPTION OF THE DRAWINGS
A method and system for generating one or more models representing a device from existing test cases described. The method and system are not intended to be restricted to any particular form or arrangement, or any specific embodiment, or any specific use, disclosed herein, since the same may be modified in various particulars or relations without departing from the spirit or scope of the claimed invention herein above shown and described of which the device or method shown is intended only for illustration and disclosure of an operative embodiment and not to show all of the various forms or modifications in which this invention might be embodied or operated.
The present disclosure is an extendible, scalable and reliable solution to the above mentioned problems. It can further be adapted or reused to function across various domains and industries for different problems and anomalies. Further, it is modular and object oriented since custom units can be plugged in to extend the functionality of the system. It also offers role based security and personalized views in a collaborative environment. Overall it offers a reliable and low cost solution to the above mentioned problems.
A premise for the technology m this disclosure is the availability of documentation on manual test cases for al! the functionalities of the system. The documentation comprises the entire testing procedure and data for a particular functionality in the manual test case

Figure 1 depicts the primary embodiment of the method followed in this disclosure. The procedure begins with obtaining one or more test variables and their values for each of the test cases. In a preferred embodiment, this data is stored in an excel format. However if not, then it is first converted to an excel format. In a preferred embodiment this manual test case data exists for all functionalities of the device.
Once transformed, this data is processed to create unified or separate models. In a preferred embodiment, the user or tester is prompted to specify whether the model is to be unified or a separate model for each test case. During processing, the test cases are executed using the values of the test variables. Each test variable value combination from a given state will lead to another state in the system execution flow.
Next, two columns depicting at least two additional variables preferably labeled 'Design Component' and 'Linked Components' are added to the excel sheet. The 'Design Component' column states the type of the component to be generated for particular step in the test case, whereas the 'Linked Components' column contains the predecessors and successors of this component. These components are preferably separated by a semi-colon.
Once these columns are added to the manual test case sheet, the values generated for these are captured during analysis of each step of each test case and they are accordingly populated. The 'Design Component' column for each step in the test case is populated based on the keyword found in that particular step. It captures each component involved in the analysis and its attributes thereof and the 'Linked Components' column for each step is populated based on number of successors and predecessor for that particular step.
On completing the iteration for all the given test cases, states of the device is then saved into a database for the next level of analysis. For each state identified in the above iteration, all existing test cases are analyzed for possible transition into the next state. The test

variable value combinations for these transitions are noted. These transitions and the sequence of the states being reached are saved into the database. On completion of the above step, transition between states and all possible interaction between the states would have been captured along with the condition and attributes for each such interaction.
Finally, the captured data is interpreted and is used along with available configuration data to form at least one model using the information captured in the 'Design Component' and 'Linked Components' corresponding to each test case. Each component is depicted and is linked to each other component it communicates with across the given test case or in all test cases depending on the requirement. Each state of each component is represented along with each other state it transitions into.
Preferably, each generated model corresponds to a separate test case. These models can preferably be unified as per the design requirements. Alternatively, each model may also singularly correspond to the entire set of test cases for the device. In a preferred embodiment the models generated are state transition diagrams
In a preferred embodiment, these models are state machine diagrams in UXF or XML format which can be viewed using Model2Test or as a plug-in which converts these into format of Rational Rose.
In another embodiment, the generated models generated for each test case can be unified to generate a single end to end testing model for the device under test. Models are preferably unified based on the common navigation points as identified such as a user's home page, inbox, etc.

Figure 2 depicts the primary embodiment of the system implemented as per the technology in this disclosure. The input is received at the receiver which is configured to obtain one or more test variables and their values in respect of at least one test case. In a preferred embodiment, this data is received in the form of an excel sheet. However if not, then a converter is coupled to the receiver which is configured to convert the received format into excel format. In a preferred embodiment, this manual test case data exists for all functionalities of the device.
In a preferred embodiment, the system is configured to receive a prompt from the user or to specify whether the model is to be unified or a separate model for each test case. During processing, an analyzer coupled to the receiver is configured to analyze the test cases using the values of the test variables
Next, a component builder connected to the analyzer is configured to add two columns depicting at least two additional variables preferably labeled 'Design Component' and 'Linked Components' to the excel sheet. The 'Design Component' column states the type of the component to be generated for particular step in the test case, whereas the 'Linked Components' column contains the predecessors and successors of this component. These components are preferably separated by a semi-colon.
Once these columns are added to the manual test case sheet, the values generated for these are configured to be captured by a component builder coupled to the analyzer during analysis of each step of each test case. The component builder is configured to populate 'Design Component' column for each step in the test case based on the keyword found in that particular step and the 'Linked Components' column for each step based on number of successors and predecessor for that particular step.

Finally, a model builder connected to the component builder is configured to use the captured data to form at least one model using the information captured in the "Design Component' and "Linked Components' corresponding to each test case. Each component is configured to be depicted and linked to each other component it communicates with. Preferably, each generated model corresponds to a separate test case. These models can preferably be unified as per the design requirements. Alternatively, each model may also singularly correspond to the entire set of test cases for the device. In a preferred embodiment the models generated are state transition diagrams
In a preferred embodiment, these models are state machine diagrams in UXF or XML format which can be viewed using Model2Test or as a plug-in which converts these into format of Rational Rose
In another embodiment, there is a unifier connected to the model builder which is configured to unify the models generated for each test case to generate a single end to end testing model for the device under test. Models are preferably unified based on the identified common navigation points such as a user's home page, inbox, etc.
This system can be used as a stand-alone application or it can be implemented into a system as a plug-in.
Figures 3A and 3B depict an example of the manual test case data and corresponding model created using the technology described in this disclosure
The embodiments described above and illustrated in the figures are presented by way of example only and are not intended as a limitation upon the concepts and principles of the present invention. As such, it will be appreciated by one having ordinary skill in the art that

various changes in the elements and their configuration and arrangement are possible without departing from the spirit and scope of the present invention as set forth in the appended claims.
It will readily be appreciated by those skilled in the art that the present invention is not limited to the specific embodiments shown herein. Thus variations may be made within the scope and spirit of the accompanying claims without sacrificing the principal advantages of the invention.

We claim:
1. A method for generating one or more models from test case information for a device
comprising the steps of:
a. obtaining one or more test variables and their values for one or more test cases;
b. analyzing each test case with the corresponding test variable values;
c. capturing each component involved in the analysts of the test case and each
other component it communicates with along with their attributes and states;
d. assimilating transitions for each component between states, interactions between
and the conditions and/or attributes for each such interaction; and
e. forming one or more models by depicting each component and linking it with
each other state it transitions into
2. A method as claimed in claim 1, wherein the manual test case data exists for all functionalities of the device
3. A method as claimed in claim 1, wherein the test case data is stored in an excel sheet
4. A method as claimed in claim 1, comprising the step of:
a. adding a first additional variable and a second additional variable to the existing test variables
5. A method as claimed in claim 4, comprising the step of:
a. populating the first and second additional variables for each test case with values obtained during its analysis
6. A method as claimed in claim 1, wherein the first additional variable stores components
generated as a result of the analysis of each test case

7. A method as claimed in claim 6, wherein the first additional variable comprises possible identifications of one or more states and their attributes
8. A method as claimed in claim 5, wherein the component are generated based on one or more keywords identified during the analysis of the test case
9. A method as claimed in claim 5, wherein the second additional variable stores predecessors and successors of each generated component
10. A method as claimed in claim 1 , wherein each generated model corresponds to a test case
11. A method as claimed in claim 1, wherein each generated model comprises to the all test cases for the device
12. A method as claimed in claim 1, comprising the step of:
a. converting the existing format of the test variables and their values to XML format;
13. A method as claimed in claim 1, comprising the step of:
a. unifying multiple models generated for each test case to single model corresponding to the device
14. A method as claimed in claim 13, wherein the single model is unified based on common navigation points for the multiple models
15. A method as claimed in claim 1, wherein the model is a state transition diagram

16. A system for generating a mode! from test case information for a device comprising of:
a. receiver configured to obtain one or more test variables and their values for one
or more test cases;
b. analyzer coupled to the receiver and configured to analyze each test case with
the corresponding test variable values;
c. component builder coupled to the analyzer and configured to capture each
component involved in the analysis and each other component it communicates
with; and
d. model builder coupled to the component builder and configured to form a model
by depicting each component and linking it with each other component it
communicates with
17. A system as claimed in claim 16, wherein the manual test case data exists for all functionalities of the device
18. A system as claimed in claim 16, wherein the test case data is stored in an excel sheet
19. A system as claimed in claim 16, wherein the component builder is configured to add a first additional variable and a second additional variable to the existing test variables
20. A system as claimed in claim 19, wherein the component builder is configured to populate the first and second additional variables for each test case with values obtained during its analysis
21. A system as claimed in claim 19, wherein the first additional variable stores one or more components generated as a result of the analysis of each step of the test case
22. A system as claimed in claim 21, wherein the component is generated based on one or more keywords during the analysis of the test case

23. A system as claimed in claim 21, wherein the second additional variable stores predecessors and successors of each generated component
24. A system as claimed in claim 16 , wherein each generated model corresponds to a test case
25. A system as claimed in claim 16, wherein each generated model comprises to the all test cases for the device
26. A system as claimed in claim 16, comprising of:
a. converter coupled to the receiver and configured to convert the existing format of the test variables and their values to excel format;
27. A system as claimed in claim 16, comprising of:
a. unifier coupled to the model builder and configured to unify multiple models generated for each test case to single mode! corresponding to the device
28. A system as claimed in claim 27, wherein the single model is unified based on common identified navigation points for the multiple models
29. A system as claimed in claim 16, wherein the model is a state transition diagram
Dated this 30th day of June 2011
Of Anand and Anand Advocates Agents for the Applicant