Conditions enhancement: option to exclude unfulfilled conditional sections from report
Please consider adding an option to exclude unfulfilled conditional sections from report. For example, in my tests, I'm typically running just one section from let's say 5 or 10, but report still shows all these unfulfilled sections. They not only clutter the report with irrelevant sections (no matter they are grayed out) but they also make the report unnecessary big.
Thank you for your input.
We are currently investigating a few improvements for the conditions feature.
We still think that conditions should almost never be used in black box testing, but we see them as a tool that can and should be used in a few exceptions. Therefore we don’t want to build upon what we currently have to make it a full feature. However, we will consider a few Quality of Life improvements.
The Ranorex Product Management Team
W. Triebkorn commented
some explanation about our use case of the Conditions.
The user of our App can have different roles, e.g. "Viewer", "Service", "Admin". Test cases defined in Ranorex shall be executed under every possible role. The list of the roles is defined in a Datasource (Simpletable).
But some test cases are only valid for specific roles. Therefore we use the Condition.
+ works for all roles
+ all entries of Datasource are used
+ works only for roles Admin and Service
+ for role Viewer some UI elements are not visible
+ the entry Viewer of Datasource is filtered out by Condition
+ works only for role Viewer
+ the entry Admin and Service of Datasource are filtered out by Condition
We would like to have the possibilty to mark and/or hide these "blocked" test cases in the Report of the Test Run.
Or do you purpose a different approach for such test scenario?
I want to note that with large test suites, this becomes a huge problem and makes reports extremely difficult to review.