Tosca Execution Logs: How to Read and Debug

Tricentis Tosca is a powerful test automation tool used for functional, regression, and end-to-end testing across a wide range of applications. While Tosca’s intuitive model-based testing makes automation accessible, understanding and interpreting execution logs is essential for efficient debugging and maintenance of your test cases.

In this blog, we’ll break down Tosca execution logs, how to navigate them, and tips for debugging common issues during test execution.


What Are Tosca Execution Logs?

Tosca execution logs are generated after running test cases, test folders, or test sets. They record detailed step-by-step execution information, including:

  • Test case names and hierarchy
  • Execution statuses (Passed, Failed, Warning, Error, etc.)
  • Actions performed on the system under test (SUT)
  • Values used in test steps
  • Failure messages or screenshots (if enabled)

These logs are stored in Tosca’s ExecutionList and can be accessed from the Execution tab or via the Execution View.


How to Access Execution Logs

After executing a test:

  • Go to the Execution section in Tosca Commander.
  • Select the appropriate ExecutionList or ExecutionEntry.
  • Right-click and choose View Results or simply double-click the test execution entry.
  • The Execution Log Viewer will open, showing a hierarchical tree structure of the executed test cases.

You can also find logs in the Tosca Results folder or export them as HTML or PDF reports for sharing and analysis.


Reading the Log Structure

Each execution log has a structured layout:

  • Root Node: Typically the ExecutionList or TestSet.
  • Test Cases: Listed hierarchically, showing folders, test cases, and test steps.
  • Test Steps: Show actual execution details, including:
  • Action performed (e.g., Click, Input, Verify)
  • Control name (e.g., Button, TextBox)

Test data used

Result (Passed/Failed/Warning)

Each step also contains ExecutionDetails, which provide timestamped logs, error descriptions, and technical logs if enabled.


Debugging with Tosca Logs

When a test fails or returns a warning, the log is your primary tool for diagnosing the issue. Here’s how to use it effectively:


1. Trace the Failure Path

Expand the test case and go to the step that failed.

Read the error message and note which control, input, or validation failed.

Check if the expected value and actual value mismatch.


2. Check Technical Information

Right-click on a failed test step and select Details to open the execution info.

This section often includes technical identifiers (like XPaths), test configuration, or environment details.


3. Review Screenshots

If screenshot logging is enabled, failed steps will include a visual snapshot.

Use this to verify whether the application was in the expected state.


4. Use Log Filters

Apply filters to view only failed or warning steps to quickly isolate problem areas.


Tips for Effective Debugging

  • Enable detailed logging in your Tosca settings if you need more granular traceability.
  • Use TestCaseLogInfo modules to print custom messages into the log during execution.
  • If working in a team, export logs and attach them to defect reports in tools like JIRA or ALM.
  • Regularly review execution logs during test development to catch configuration issues early.


Conclusion

Tosca execution logs are more than just records—they are powerful diagnostic tools that help testers identify failures, understand test behavior, and improve test quality. By mastering log navigation and interpretation, you can significantly enhance your efficiency in maintaining and troubleshooting automated test cases in Tosca.

Learn TOSCA Training Course
Read More: Tosca API Testing: Step-by-Step Guide


Visit Quality Thought Training Institute in Hyderabad
Get Direction

Comments

Post a Comment

Popular posts from this blog

Tosca vs Selenium: Which One to Choose?

Choosing the right test automation tool can make or break the efficiency of your QA process. Two widely discussed tools in the test automation space are Tosca by Tricentis and Selenium, the open-source web automation framework. While both tools aim to automate testing and accelerate software delivery, they cater to different needs and teams. In this blog, we’ll provide a comprehensive comparison between Tosca and Selenium to help you decide which one suits your project best. Overview Selenium is an open-source framework primarily used for automating web applications. It supports multiple languages (Java, Python, C#, etc.) and browsers, making it ideal for custom, flexible automation solutions. Tosca, on the other hand, is a commercial test automation tool that supports model-based testing, API testing, mobile, desktop, and even SAP testing. It's designed for enterprise-grade testing with minimal scripting. Key Comparison: Tosca vs Selenium Feature          ...
Read more

Flask API Optimization: Using Content Delivery Networks (CDNs)

When building APIs with Flask, performance and speed are key metrics that directly affect user experience and application scalability. One powerful but often overlooked way to enhance these metrics is through the use of Content Delivery Networks (CDNs). While CDNs are traditionally associated with delivering static assets like images, CSS, and JavaScript, they can also play a significant role in optimizing your Flask-based APIs. What Is a CDN? A Content Delivery Network is a globally distributed network of proxy servers that cache content closer to end-users. Instead of every user hitting your central Flask server, a CDN enables them to access cached responses or assets from a nearby server, significantly reducing latency and improving response times. Benefits of Using CDNs with Flask APIs 1. Reduced Latency Latency is the time it takes for a request to travel from the client to your server and back. By caching static or semi-static responses at edge locations, CDNs reduce the distance...
Read more

Using ID and Name Locators in Selenium Python

When automating browser tasks with Selenium in Python, one of the first challenges is identifying and interacting with web elements. Selenium offers multiple strategies for locating elements, and two of the simplest and most effective methods are using the ID and Name locators. These locators are fast, reliable, and easy to use, making them ideal for beginners and experienced testers alike. In this blog post, we’ll dive into how ID and Name locators work in Selenium Python, provide examples, and share best practices to help you write clean and maintainable test scripts. What Are Locators in Selenium? Locators in Selenium are methods used to find elements on a web page. Selenium supports several locator types, including: ID Name Class Name Tag Name Link Text CSS Selector XPath Among these, ID and Name locators are often the most efficient because browsers optimize them for speed and accuracy. Setting Up Selenium with Python Before using locators, ensure you have Selenium installed: bash...
Read more