Yes, we are running groovy scripts for some of the cases. How do we figure out that the script is the culprit, its pretty hit or miss on which test case decides to stop on us and we are using at least one groovy script for each test case.
Yes on the data loops and datasources. Loops meaning looping through a datasheet with no more than 13 rows, albeit many more columns in some instances.
As for running step/cases in parallel - no, we are currently not doing that. We are just starting out with the tool and just grasping how to generate the tests.
Also, not performing and sleep/waits that may cause a delay of some sort.
StaffI would say: log a support ticket. Your problem sounds like it is more about what you are calling with your script rather than the script itself, but it is hard to tell.
Let me know how that goes!
