Hi Avinash,
The approach that you are using is fine, if we have limited test cases. In our case, we have 250+ cases and those many sub-process steps cannot be created
Have found solution for this problem. Whenever a sub-process is getting executed, following 2 properties are getting created.
Property1: "lisa.subprocess.<<sub process/test case path>>.tst.xml.doc";
Property2: "lisa.hidden.subprocess.Execute Test Case.testcase.cache",
Both are not string valued properties rather it contains objects. Property 1 contains test/sub-process document object and property 2 contains test case/sub-process property. So we need to create a custom script to load these properties dynamically, before the sub-process step execution. Have achieved this with below piece of code.
String prop1 = "lisa.subprocess.<<sub process/test case path>>.tst.xml.doc";
testExec.setStateValue(prop1, com.itko.lisa.test.TestCase.openTestCaseDoc(<<test case path>>));
testExec.setStateValue("lisa.hidden.subprocess.Execute Test Case.testcase.cache", com.itko.lisa.test.TestCase.loadTestCase(com.itko.lisa.test.TestCase.openTestCaseDoc(<<test case path>>), "project.config"));
Now I do have only one sub process step (which will call multiple test cases for each iteration) in my driver script and above script is placed before sub-process step.
Note: Above script should not be executed for first iteration. For the first iteration, directly run the sub-process step and from 2nd iteration update the properties values through above script.
Please let me know (if you have time and patience to test this ), if this approach works fine for you.