Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

MultipleWidgetFoundException within TreeItemDriver #17

Open
GoogleCodeExporter opened this issue May 4, 2015 · 6 comments
Open

MultipleWidgetFoundException within TreeItemDriver #17

GoogleCodeExporter opened this issue May 4, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Make a Tree with a TreeItem which has the same Name and Value
2. Write a test to select or locate this TreeItem
3. You will get the above mentioned exception

TreeItemDriver throws this exception if he found out, that a string appears in 
2 Items but there is no check if this widget/item is the same so he throws a 
MultipleWidgetFoundException

See the code line:
if (found == null) {
   found = items[row];
}
else
 throw new MultipleWidgetsFoundException("Multiple tree items found for \'" +nodeText
    + "\' in " + getAllItemText(textForItems));


I made little changes and would say this is a bug in WindowTester. 
Patch is attached.

Best regards,
Falk

Original issue reported on code.google.com by [email protected] on 18 Jan 2013 at 1:31

Attachments:

@GoogleCodeExporter
Copy link
Author

Hi Falk,

Thanks for your patch. Could you add a test case for it?

Regards,

Frederic

Original comment by [email protected] on 17 Feb 2013 at 12:57

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Hi Frederic,

i have created a simple plugin for eclipse - it was the easiest way for me. It 
just show up a view with a 2 Column Tree - during coding i rethought maybe it 
is our fault to use a Tree in this combination rather than a table .. 

Let me hear what you think, i have attached the entire project as zip :)

Regards,
Falk

Original comment by [email protected] on 18 Feb 2013 at 12:34

Attachments:

@GoogleCodeExporter
Copy link
Author

Issue 21 has been merged into this issue.

Original comment by [email protected] on 6 Mar 2013 at 1:07

@GoogleCodeExporter
Copy link
Author

As we moved on to Eclipse 4.3.2 version for our application, i found out, that 
this fix wasn't included in the latest community fixes. 

Is there a reason why or was this just forgotten?

Regards,
Falk

Original comment by [email protected] on 17 Sep 2014 at 11:51

@GoogleCodeExporter
Copy link
Author

Hi Falk,
If I remember correctly there were still issues with the TreeDriver that kept 
me from committing the changes. I'll take another look...

Regards,

Fred

Original comment by [email protected] on 23 Sep 2014 at 10:01

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant