Tosca Execution Logs: How to Analyze and Debug

Analyzing and debugging Tosca execution logs is essential for identifying test failures, performance issues, and script errors. Here's a guide to help you understand and effectively work with Tosca execution logs.


✅ What Are Tosca Execution Logs?

Tosca generates execution logs whenever you run test cases via Tosca Commander, Tosca CI, or Tosca Executor. These logs include details such as:


Execution status (Passed/Failed)


Test steps and results


Error messages and stack traces


Timestamps


Test environment details


πŸ“ Where to Find Tosca Execution Logs

Logs can be accessed via:


Tosca Commander → Execution section


ExecutionLists → Right-click → View Execution Log


File system: If configured, Tosca stores logs in TBox\Logs or a custom output folder


πŸ” How to Analyze Execution Logs

1. Open the Execution Log

In Tosca Commander:


Go to the ExecutionList or Execution Section.


Right-click a test case and select “View Execution Log”.


2. Check the Result Column

🟒 Passed: Everything worked as expected.


πŸ”΄ Failed: Indicates an issue—click on it to expand details.


3. Read the Error Message

The Error Details section will show:


The failed TestStep


The actual vs expected values


Possible exception messages or timeout errors


4. Trace Execution Path

Review the sequence of executed steps:


Use step-by-step navigation.


Confirm whether the test failed due to data issues, synchronization, object recognition, or logic errors.


5. Use the Log Viewer

Tosca has a built-in log viewer with filtering, searching, and timeline views:


Sort by timestamps or status


Search specific terms (e.g., Timeout, Not found)


πŸ›  Tips for Debugging

Issue Type Debugging Tip

Object not found Verify TestObject and technical identification (XPath, ID, etc.)

Timeout errors Increase wait time or use dynamic wait conditions

Assertion failure Compare actual vs expected values—review input data

Script errors Check custom modules or business component logic

Data issues Validate input data (use TestCase logs or DataBindings)


πŸ“€ Exporting Logs

To export logs for reporting or debugging:


Right-click Execution List → Export → HTML/XML


Or use Tosca Commander Reporting integration (Excel, PDF)


πŸ§ͺ Optional: Use Tosca Continuous Integration (CI) Logs

If you're using Tosca with CI tools like Jenkins:


Execution logs are stored in the CI environment


Use Tosca CI Client to generate JUnit-compatible logs


Check .trx or .xml files for failure reasons


🧭 Summary Checklist for Log Analysis

✅ Open Execution Log

✅ Identify failed step(s)

✅ Read error message

✅ Check test data & conditions

✅ Review object identification

✅ Re-run test with logging enabled if needed

Learn Tosca Training in Hyderabad

Read More

Tosca Recorder: How to Use It Effectively

Tosca XPath: Locating Elements Like a Pro

Visit Our IHUB Talent Training Institute in Hyderabad

Get Directions

Comments

Popular posts from this blog

How to Install and Set Up Selenium in Python (Step-by-Step)

Feeling Stuck in Manual Testing? Here’s Why You Should Learn Automation Testing

A Beginner's Guide to ETL Testing: What You Need to Know