AUTOMATED TEST FRAMEWORK

[kishorek9987311]

Hi all,

I am currently automating the Problem module, including its stages and associated tasks, using ATF. While executing the test, I am encountering the following error:

“Failed to report client batch process. Test will time out.”

This issue occurs in both SOW and Native view.

Even when I try a simple validation—such as checking the Priority field values in the Problem record (with only 23 steps)—I still receive the same error. However, for the Incident module, I have successfully executed tests with 25–26 steps without any issues.

In the Step Results tab, all steps are showing as Success, which is confusing. I’m not sure whether this behavior is expected or if there is an issue with my test logic.

To troubleshoot, I also tried increasing the Test Runner Heartbeat Interval system property from 60 to 1200, but it did not resolve the issue.

I have attached screenshots for reference. Could someone please help me understand what might be causing this and how to resolve it?

If anyone is available, we can also connect briefly to discuss this further

[SAI VENKATESH]

Hi @kishorek9987311 

You need to go to the step that is giving the error and in the related links of the step: there will be related link to accept the errors. when you accept it from next time you will not get any errors.

Thanks and regards

Sai Venkatesh

[kishorek9987311]

Hi @SAI VENKATESH  

Thanks for the reply.

Do you mean “Add all errors to the ignore list”? I have already tried that.

All steps in the Step Results and Test Logs are showing Success. However, the last two steps—Record Query and Open Existing Record—are showing as Skipped. I have attached a screenshot for reference.

On the Client Test Runner page, after all steps are executed, I briefly see a message for a millisecond saying:
“Failed to report client batch process. Test will time out.”

Is this expected behavior, or is there something else I need to fix?

[PaulBecker]

That ATF timeout error with "Failed to report client batch process" is tricky, especially since all steps show success but the last ones get skipped. Common in Problem module tests involving SOW. Try checking the browser console for client-side errors during run, or disable any client scripts temporarily on the form. If that doesn't help, log a support case with those screenshots.