Analyzing and debugging Tosca Execution Logs is an essential part of maintaining test automation reliability. Tosca (by Tricentis) generates detailed logs after each test execution, which can help you quickly pinpoint failures, inefficiencies, or configuration issues.
Here’s how to analyze Tosca execution logs effectively and debug issues step-by-step:
✅ 1. Types of Tosca Logs
Tosca creates multiple types of logs depending on what you're doing:
Log Type Description
Execution Log Shows step-by-step result of the test case execution (passed/failed/skipped)
ExecutionDetails Log Detailed log of each test step with technical messages
Log Files (.xml/.trx) Generated for integrations (e.g., Azure DevOps)
ToscaCI Log Logs when running via ToscaCI or command line
Agent Logs For distributed execution or Tosca Distributed Execution (DEX)
📁 2. Where to Find the Logs
In Tosca Commander: After test execution → go to the Execution tab → right-click on the test case or folder → "View Execution Log".
Log Files on Disk: Default path is usually:
makefile
Copy
Edit
C:\ProgramData\TRICENTIS\ToscaTestsuite\7.0.0\Logs\
(Check your Tosca version; folder names may vary.)
DEX Execution Logs: On the DEX machine (agent) or central controller, typically under:
makefile
Copy
Edit
C:\ProgramData\TRICENTIS\DEXAgent\ExecutionLogs\
🕵️ 3. How to Read the Execution Log
Execution Log View in Tosca:
Element Meaning
✅ Green Test step passed
❌ Red Test step failed
⚠️ Yellow Warning or conditionally passed
➕ Expand See more details for each step
Click each step to view:
Test step details
Expected vs actual result
Error message or exception
Execution time for each step
🛠️ 4. Debugging Failed Test Steps
a. Check Error Message
Look at the red failed step:
Does it say "Object not found", "Timeout", or "Verification failed"?
Common errors:
Control not found: UI element is missing or not loaded
Timeout: Application is slow or control is dynamic
Verification error: Value did not match the expected result
b. View ExecutionDetails
Right-click the failed step → “View ExecutionDetails”
Shows technical logs: control IDs, recognition parameters, buffer values
Good for debugging dynamic elements or misconfigured modules
c. Check Modules
Open the module used in the step
Re-scan if the UI changed (especially for dynamic applications)
🔄 5. Enable Logging for Deeper Debugging
a. Enable Diagnostic Logs
In Tosca Commander:
Go to Project → Settings → Engine → Logging Level
Set to Diagnostic to capture more info
Note: Can slow down execution, use only during troubleshooting.
b. Enable ToscaCI Logging
If you're running tests via ToscaCI (CI/CD tools):
Check the ToscaCI.log under the %AppData% or program data folder
Use this to debug pipeline failures or command-line issues
🧪 6. Use Tosca Log Viewer (Optional Tool)
If dealing with exported logs (.xml format):
You can open them using the Tricentis Log Viewer (a standalone tool)
Helpful for support teams and when sharing logs with Tricentis
💡 7. Best Practices for Troubleshooting
Tip Benefit
Use WaitOn conditions Prevent timing issues in dynamic UIs
Avoid using Hard Waits (Wait(10)) Use smart waits like WaitOnAttribute or WaitOnExistence
Use Verification steps early Catch issues before interacting with broken UI
Keep modules updated Changes in UI often break test steps if modules are outdated
Log and buffer important values Helps validate input/output and debug mismatches
📦 Bonus: Common Error Codes and What They Mean
Code Meaning Fix
1001 Control not found Check locator, control wait, dynamic IDs
1005 Timeout Use wait conditions, improve app performance
2001 Verification failed Check expected value vs actual
3000+ Engine errors Check module configuration or scripting errors
✅ Summary
Use Execution Logs and ExecutionDetails to trace test flow and find root causes.
Enable diagnostic logging for deeper insights.
Keep modules and test steps in sync with the application under test.
Automate smart waits and validations to reduce flakiness.
Learn Tosca Training in Hyderabad
Read More
Tosca Recorder: How to Use It Effectively
Tosca XPath: Locating Elements Like a Pro
Automating Desktop Applications Using Tosca
Tosca and SAP: End-to-End Test Automation
Visit Our Quality Thought Training in Hyderabad
Subscribe by Email
Follow Updates Articles from This Blog via Email
No Comments