Community
Participate
Working Groups
At the moment the Test Case Editor only show two hierachy levels. The Test case itself and its direct references. When I want to take a deep look into the hierachy I always have to open new editors and have to switch between them. I think its better if the complete hierarchy of the Test case can be seen (icons of level 3 should be grey to indicate they cannot be edited) because I have to break in workflow. Furthermore it would be nice if the properties and componet views can should their values in the given context. Example if I set the value for an text check in the test case reference, I can see this value in the test step at every level below and not the parameter name.
At the moment, the best way of doing this would be to use the browsers to look through the full hierarchy, as they show the properties / component names as well, and it means you don't have to open editors just to look.
(In reply to comment #1) > At the moment, the best way of doing this would be to use the browsers to look > through the full hierarchy, as they show the properties / component names as > well, and it means you don't have to open editors just to look. Yes, but I am working in the editor not in the test case overview and there is not so much space in the view as it is in the editor. In addition it is very confusing if I want to edit something if I always have to jump between the browser and the test case editor. The properties just show the static values (parameters and component names) not the concrete values in the given context of the test case I am working.
Having discussed this with the team, the original enhancement request of being able to expand the children of nodes in the editor will not be implemented. The reasons for this are: - Performance - User Confusion about why level 3 nodes can't be edited However, some kind way of seeing details about the steps, parameters and component names in a module without having to leave the editor would be a good idea.
After further discussion, this request is being rejected due to a lack of clarity of what information should be visible and a lack of consensus about whether wanting to see this information is a question that can be resolved by test design.
