Forum Discussion

kate4's avatar
kate4
New Contributor
10 days ago

Running test gets 'stuck' and have to restart ReadyAPI

Have been running into an issue when creating new test cases and after a handful of times running the test, it gets 'stuck'. You can attempt to click the red stop button but it does not appear to do ...
CarlosValcarcel's avatar
CarlosValcarcel
Icon for Staff rankStaff
10 days ago

So here are a few possibilities:

  • Infinite loop or hanging step
    Even if it appears steps are done, a Groovy script or a loop might still be running (sleep/wait) and preventing the Test Case from completing.
  • Thread exhaustion / parallel overload
    If you are executing many steps/test cases in parallel, ReadyAPI’s thread pool might be consumed, causing UI “stop” buttons to be unresponsive. The docs mention this exact scenario.
  • Stop button doesn’t “force kill” all running threads
    The UI stop button may halt the test sequence execution but might not kill background threads or loops inside Groovy. That leaves the Test Case indefinitely “Running”. There’s a community post lamenting this inability to forcibly stop Groovy loops.

A question:

  • are you running any Groovy scripts?
  • any sleep/waits?

It’s possible a bug in this version affects certain structures of Test Cases (especially those with loops, datasources, or chained calls), but I would reserve judgment on that. :)

Let me know how it goes!

  • kate4's avatar
    kate4
    New Contributor
    10 days ago

    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.

    • CarlosValcarcel's avatar
      CarlosValcarcel
      Icon for Staff rankStaff
      3 days ago

      I 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!