I did not get answer on how to get current iteration id from the above link you shared as it leads to test case variables page which has no information on current iteration ID.
Can you re share or mention how to current iteration number.
Why the method “B. Execute from a test case” has been ignored out of the offical document?
I guess a recent change at v6.3.0 is related to it:
At v6.3.0, a fix for “An issue related to running a test suite with too large test data” was included. I suppose the Katalon team was so deeply devoted into the method “A. Execution from test suites” that they forgot all about the method “B. Execution from a test case”.
How about using a variable to bind Excel data at the Test Case level with optional bindings at Test Suite level (will override any variables set in Test Case level) if you had a need (eg different data)? Does this description make sense?
now that I look, I see that what I am describing is very close to a DZone article - https://dzone.com/articles/data-driven-testing-approach-with-katalon-studio. My only change is at the third step though, instead of creating variables that have a string type, I use a test data value.
The variable used in test case for example:
Name = Var_CustName
Type = Test Data Value
Default value = findTestData(“Customer_Details”).getValue(“CustName”, 1)
Part A of that article is then used to bind variables at test suite level.
I only mention this approach as the DZone article seems to give a much simpler approach than Katalon’s own documentation but I wonder if it is affected by script length issue mentioned, when test data includes many rows.
@Dan_Bown using ‘findtestdata’ will ignore any binding. it is just the programatically way of using certain testdata, instead of maping it. and yeah, this approach may not create the ‘large code issue’ since at the runtime the behaviour is different, the data is iterated during the execution phase, not generated during the compile phase