TestOps isnt displaying any test results

Hi All, need help

I scheduled a run from Testops

Initially, it was running and displaying the pass 5, failed 0, etc.

But after the complete run, it is not displaying anything?

Pls. suggest

Thanks

1 Like

1. Check if the execution actually completed successfully

First, confirm in TestOps → Executions:

  • Open the execution record

  • See if the status is Completed / Finished or if it shows Stopped / Error / In Progress

If it’s stuck in Running or Unknown, TestOps may not have received the final report.

2. Verify Katalon Studio is properly integrated with TestOps

In Katalon Studio:

  1. Go to Project → Settings → Katalon → TestOps

  2. Make sure:

    • TestOps URL is correct

    • You are logged in

    • The correct Project ID is selected

  3. Click Test Connection to confirm it works

If authentication expires, TestOps may show partial results initially and then clear them.

3. Make sure reports were generated and uploaded

After execution:

  • Check this folder in your project:

    Reports/
    
    
  • Confirm that the execution folder contains:

    • JUnit_Report.xml

    • execution.properties

    • .log files

If these files are missing or incomplete, TestOps cannot display pass/fail data.

4. Look at the console log for TestOps upload errors

During execution, watch the Console in Katalon Studio (or CI logs) for messages like:

  • Failed to upload report to TestOps

  • 401 Unauthorized

  • 403 Forbidden

  • Timeout while uploading execution result

Even if the test ran successfully, upload failure = no results shown.

2 Likes

hi @anandkumar.venkatara

if the counts were visible during execution but disappeared after completion, the usual causes are upload or filtering issues

below is a short checklist you can try, and some info to share if you want more help.

  • Check UI filters and date range on the TestOps Executions page. Make sure no filters (status, tags, user) or a narrow date range are hiding the finished run.
  • Confirm you are in the correct TestOps project and workspace. Runs can be uploaded to a different project by mistake.
  • Look at the run entry on the Executions page.
    • Does a run record exist (even if empty) or is it completely missing?
    • Note the execution ID if you see it.
  • Inspect the agent / CI job logs for upload messages.
    • Search for keywords like "upload", "Upload execution", "Failed to upload", or "Exception".
    • If upload failed, you will usually see an error there.
  • If you used a TestOps agent, restart the agent and re-run a quick small job to see if results upload correctly.
    • Also check the agent version compatibility with the TestOps server.
  • If you scheduled via CI (Jenkins/GitLab/etc.), check the CI console output for any result upload steps and errors.
  • Check user permissions and retention/cleanup policies in TestOps.
    • Results may have been deleted automatically if retention is configured aggressively.
  • Verify network access and API token validity on the machine that ran the tests.
    • Expired or invalid tokens will prevent upload.

if the issue persists kindly share your:

  • Katalon Studio or Katalon Runtime Engine version, and TestOps agent version
  • How the run was scheduled
    • (TestOps scheduler, Katalon Agent, Jenkins, other)
  • Execution ID or a screenshot of the Executions page where the run should appear
  • Relevant log snippets showing upload success or failure
    • (paste the lines around the upload step)
  • Any error messages seen in the TestOps UI or CI logs
2 Likes
  1. TestOps Connection
    • Ensure the machine/agent running the test has stable internet access.

    • Verify the TestOps API key is still valid and correctly configured in Katalon Studio / KRE.

  2. Execution Upload Failure
    • Check the execution log at the end of the run.

    • Look for messages like:

      • Failed to upload execution result to TestOps

      • 401 / 403 unauthorized

      • Timeout while syncing data

  3. KRE / Studio Version Mismatch
    • Make sure your Katalon Studio or KRE version is compatible with the TestOps project.

    • Try upgrading to the latest stable version.

  4. Scheduled Run Environment
    • If running via CI (Jenkins, GitHub Actions, etc.), ensure:

      • -testOpsProjectId and -apiKey are passed correctly.

      • The execution is not being terminated early (job timeout).

  5. TestOps UI Delay
    • Sometimes TestOps takes a few minutes to process the execution.

    • Refresh the page or check under Executions → All runs.

  6. Project Binding
    • Confirm the Katalon project is properly linked to the correct TestOps project.

    • Rebind the project if needed.

1 Like

Try to Re-Import the summary.

You can do it by clicking on the ellipses (3 dots ) corresponding to the test run

1 Like

Quick Solution

Results not displaying after scheduled run completes is typically caused by:

  1. Page not fully loaded → Refresh the page (F5 or Ctrl+R)
  2. Results still processing → Wait 1-2 minutes for TestOps to aggregate results
  3. Wrong view → Go to Executions > Run and click on your test run ID to view the Summary tab (shows pass/fail counts)

Troubleshooting Steps

  1. Navigate to Executions > Run in TestOps
  2. Click on your scheduled test run ID
  3. Check the Summary tab first (displays results counts)
  4. If empty, click Test Results tab to see individual test details
  5. Clear browser cache and reload if still blank
  6. Verify the run status shows “Completed” (not “Running” or “Error”)

If Results Are Still Missing

  • The test execution may have failed to upload results to TestOps
  • Check your agent logs (if using TestCloud) for execution errors

References:

Hi Akshay

Tried re-import, but its still the same

@anandkumar.venkatara bro, your session seems to Cancelled.

It is clear from here.

Katalon does not display the results for cancelled test runs.

If you want to see the details you can click on the Sessions tab and check the details.

If you need further info i think you should share the details in the Sessions tab, it could be more helpful in assisting you.

Ok Thanks

But I didn’t cancel any, not sure

maybe it was cancelled automatically during the test execution

Hi Anand,

Can you please share a screenshot of the TestOps executions? I want to see the execution status—whether it is displayed as terminated, failed, or pending. Also, are you executing mobile automation using Web Automation?

If not, please try the following solution: before execution, select KRE 10.2.3 and then run the tests.

Thanks,

Osama

Ideally it should not get cancelled on its own, until your test cases are lengthy and your execution time has exceeded the suite execution timeout.

Here is reference for you.

1 Like

Thanks everyone for the valuable suggestions

Identified the issue - it was time-out issue, which was set to 180min. [by default]

Now, I will reset this and retry

2 Likes

hi @anandkumar.venkatara

so the issue is on the timeout configuration? increasing it and solve the issue?