ATF Test Step Status is Failure even when test logs are sucessfull

[bhaavani]

Hi Team,

I created a ATF and it ran successfully. However the Test Result status is showing as "Failure" with no Failure Details. I also added the errors to "Warning and Ignored" List. Please find the below screenshots. Can you please help me how to fix this issue ? My test result status should be successful. 

Thanks in advance

[Anupam1]

Hi @bhaavani,

Common Causes of ATF "Failure" with No Details

1. Client-side errors not logged properly:
• These may include JavaScript errors or UI rendering issues.
• If the error isn’t in the "Allowed Client Errors" table, ATF marks the test as failed—even if steps pass.
2. Using unsupported UI (e.g., Next Experience or Workspace):
• ATF has limited support for Configurable Workspaces or Next UI.
• Tests may fail silently if steps interact with unsupported components.
3. Missing or misconfigured test data:
• If a test step relies on data that wasn’t created or loaded properly, it may fail without logging a clear error.
4. Timeouts or skipped steps:
• A step may have timed out or been skipped due to a dependency.
• Check the Test Result record for any skipped or pending steps.

How to Fix It

Step 1: Check the Test Result Record

• Go to Automated Test Framework > Test Results.
• Open the failed result and inspect:
• Client Error Details
• Failure Details
• Step Execution Logs

If these are blank, proceed to deeper troubleshooting.

Step 2: Review "Allowed Client Errors"

• Go to Automated Test Framework > Allowed Client Errors.
• Ensure the exact error string (case-sensitive) is listed.
• If you added a generic error, it may not match the actual client error.

 Step 3: Add Logging to Your Test

• Add a Log Message step before and after critical actions.
• This helps pinpoint where the test might be silently failing.

Step 4: Use "Custom UI Step" for Workspace

• If you're testing in CSM/FSM Workspace, use Custom UI Step instead of standard form steps.

 Step 5: Try Running in Standard UI

• If possible, run the test in Classic UI to see if it passes.
• This helps isolate whether the issue is UI-specific.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Best,

Anupam.

[Sardash]

@bhaavani - Please find below possible reasons for failure -

1.  ATF evaluates the step based on assertions defined in the test step. If the assertion (e.g., field value, UI element state) does not match the expected value, the step fails even if the script runs successfully. Open the failing step and verify the expected condition. Does it match what the logs show?

2. The UI or data might not be fully loaded when the assertion runs, so increase the timeout seconds wherever required

3. The expected value in the test step might not match the actual value in the instance. For example, checking for a field value that was never set. Run the test in debug mode to see the actual values being compared.

4. If a previous step fails or is skipped, dependent steps may fail even if their logs look fine. Run the test in debug mode to see the actual values being compared.

If my response helped, please mark it by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

[bhaavani]

Hi @Anupam1  and @Sardash ,

Thanks for your reply. Below is the client error I am receiving. I added them to ignore list as well. However still the test result showing as "Failure" and all the test steps are successful. Please help here

Thanks in advance

[Anupam1]

Hi @bhaavani ,

Root Cause: HTML Rendered Instead of JSON or Script

The error Unexpected token '<' typically means that the browser tried to parse an HTML response as JavaScript or JSON. This often happens when:

• A script or AJAX call expects JSON but receives an HTML error page (e.g., 404, 500).
• A resource fails to load and returns a login page or error page instead.
• A widget or UI component is misconfigured or not supported in the test context.

Even though you've added this to the Allowed Client Errors, ATF may still mark the test as failed if:

• The error occurs multiple times in rapid succession.
• The error is tied to a critical rendering failure (e.g., page not loading properly).
• The error is not fully matched in the Allowed Client Errors table (case-sensitive, exact match required).

How to Fix It:

1. Confirm Exact Error Match in Allowed Client Errors

• Go to Automated Test Framework > Allowed Client Errors.
• Ensure the error string is exactly:

Uncaught SyntaxError: Unexpected token '<'

• Make sure the Browser field matches (e.g., Edge 42.42000.0).
• If you added a broader or partial match, ATF may not treat it as ignored.

1. Use a Client Error Handler Script

• If the error is expected and harmless, you can suppress it more reliably using a Client Error Handler Script:

(function(error) {

  if (error.message === "Uncaught SyntaxError: Unexpected token '<'") {

    return true; // Ignore this error

  }

  return false;

})

Add this script to your test configuration to dynamically filter errors.

1. Switch Browser or UI Context

• Try running the test in Chrome or Firefox instead of Edge 42.
• Edge 42 is outdated and may not fully support modern UI rendering.
• If you're testing in Next Experience or Workspace, switch to Classic UI to isolate the issue.

1. Add a Log Message Step Before and After the Error

This helps confirm whether the error is impacting form load or step execution.

1. Check for Misconfigured Widgets or Broken Includes

• If the page includes a widget or script that fails to load, it may return an HTML error page.
• Check the Network tab in browser dev tools during test execution to confirm.

Optional: Script Assertion to Validate Page Load

Add a script assertion step like:

(function() {

  return document.readyState === 'complete';

})();

Thanks,

Anupam