This site requires JavaScript to be enabled

Tosca Version
IncidentLookup using list
How can we help?

Solution Suggestions

Please enter your question to get suggestions.
Boolean Operators
OR or vertical bar symbol (|)
Finds a match if either the terms exist in a document (a union using sets).
Finds a match if both terms exist in a document (an intersection of sets).
NOT, minus (-), or exclamation point (!)
Excludes documents that contain the term after NOT (a difference of sets).
Asterisk (*)
The asterisk symbol performs a multi character wildcard search.
Percent sign (%)
The percent sign performs a single character wildcard search.
Quotation marks (")
Use quotation marks to search for an exact phrase with multiple terms.
For examples and more information look at our Knowledge Base: Advanced Search On The Support Portal

How to improve readability of results in Test Execution Log?

Hi everyone,

when checking the results of failed test cases in the Execution Log, we always need to dig through a huge load of single steps.
Even though we use folders and reusable test step libraries in our test cases - the result only shows ALL the single steps without any further folder structure. That makes it very hard to read.

Is there a simple way of improving this? Am I overlooking something?
Showing only the failed test step is not a solution for us, as we also need to see the previous steps.
I would just like have the steps grouped, e.g. to show the reusable test steps which were used or the folders used in the test case.
So we could fold/unfold some parts in the results log.

Thanks for your help!


Tosca is the perfect solution

Optimize - Manage - Automate

Download Trial