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
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
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:
Go to Project → Settings → Katalon → TestOps
Make sure:
TestOps URL is correct
You are logged in
The correct Project ID is selected
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.
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.
"upload", "Upload execution", "Failed to upload", or "Exception".if the issue persists kindly share your:
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.
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
Make sure your Katalon Studio or KRE version is compatible with the TestOps project.
Try upgrading to the latest stable version.
If running via CI (Jenkins, GitHub Actions, etc.), ensure:
-testOpsProjectId and -apiKey are passed correctly.
The execution is not being terminated early (job timeout).
Sometimes TestOps takes a few minutes to process the execution.
Refresh the page or check under Executions → All runs.
Confirm the Katalon project is properly linked to the correct TestOps project.
Rebind the project if needed.
Try to Re-Import the summary.
You can do it by clicking on the ellipses (3 dots ) corresponding to the test run
Results not displaying after scheduled run completes is typically caused by:
References:
@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.
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
so the issue is on the timeout configuration? increasing it and solve the issue?