Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 413793

Summary:	RC - Tree action: select parent node missing
Product:	[Technology] Jubula	Reporter:	Markus Tiede <markus.tiede>
Component:	RC	Assignee:	Project Inbox <jubula.rc-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	enhancement
Priority:	P4	CC:	alexandra.schladebeck, torstenjanke
Version:	2.1	Keywords:	triaged
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Markus Tiede

2013-07-26 05:41:55 EDT

We should think about offering a standalone RC action on trees to relatively select a parent node (via pre-ascending) without implicitly selecting a child node afterwards.

Maybe this can be achieved by allowing an empty / special child path (indicating that no other child should be selected / checked) for the currently existing actions.

Comment 1 Alexandra Schladebeck

2013-07-31 08:06:24 EDT

Sounds like an interesting idea - I'm not sure how many people would need it though. I have a feeling it's one of those "If I need it I really need it, and if I don't, I'd never even imagine anyone needing it".

Would a current workaround be to preascend twice and then select the parent node?

Comment 2 Torsten Janke

2013-10-09 09:19:37 EDT

I just posted a topic that in the forum that asks exactly this. So I guess I fall in the "I really need it", I guess ;)

Here is the usecase: An application creates a tree and auto-selects one node based on some complicated logic. The test should ensure that the right node is selected. Problem is, the selected node is not unique on itself, I need to consider its parent node:

Root
+--- Identifying node 1
|     +--- node "abc" (auto-selected)
+--- Identifying node 2
      +--- node "abc"

I have not understood the mentione workaround, actually. I would not work to pre-ascend twice and then select the first child node - this would always result in a valid test, since I hardwire in the testcase which one the correct node is. Consider for instance: if the application (wrongfully) auto-selects the second "abc" node, then going up twice and selecting first child would result "true".

Comment 3 Alexandra Schladebeck

2013-10-09 10:56:55 EDT

Just to crosslink: here's the forum post. I posted a possible workaround there too.
http://www.eclipse.org/forums/index.php/t/543548/

Comment 4 Alexandra Schladebeck

2013-10-18 05:23:10 EDT

The workaround worked in the case of the forum, so I'm going to leave this as a P4 enhancement.

Comment 5 Alexandra Schladebeck

2013-11-20 13:25:28 EST

Since we're doing a bit of a clear-out, I'm going to close this as wontfix for the reasons mentioned in the comments. Reopen if new information or use cases come to light.

Comment 6 Oliver Goetz

2013-11-21 03:14:31 EST

Closed due to comment 5