Bug 416860 - ImageHyperlink widget is ignored. AUT Agent throws exception
Summary: ImageHyperlink widget is ignored. AUT Agent throws exception
Status: CLOSED WONTFIX
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P2 major (vote)
Target Milestone: 4.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard: stalebug
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-09-09 12:45 EDT by Michael L CLA
Modified: 2016-05-19 03:39 EDT (History)
2 users (show)

See Also:


Attachments
Code, Screenshot and Exception in one doc (29.51 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2013-09-09 12:45 EDT, Michael L CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael L CLA 2013-09-09 12:45:24 EDT
Created attachment 235317 [details]
Code, Screenshot and Exception in one doc

Hi all,

I'm trying to test an application that has weird widget. It is ImageHyperlink that when clicked opens an Menu. The screenshot is in attachment.
The code snippet where this widget is created:

// add condition icon
final ImageHyperlink addConditionLink = this.conditionWrapperComposite.addHyperLinkImage(CoreImageRegistry
				.getImage(CoreImageRegistry.IMAGE_ADD), layoutData, rulesEditControls);
addConditionLink.setData("name", "AddConditionLink");
		addConditionLink.setToolTipText(PromotionsMessages.PromoRulesDefinition_Tooltip_AddCondition);

this.addConditionMenu = new Menu(this.conditionWrapperComposite.getSwtComposite());
		addConditionLink.setMenu(this.addConditionMenu);
		addConditionLink.addMouseListener(new MouseAdapter() {
			@Override
			public void mouseDown(final MouseEvent mouseEvent) {
				addConditionMenu.setVisible(true);
			}
		});

When Jubula is in observation mode, the widget is ignored (no green highlighting) and as soon as I click on the widget, the exception is thrown in the AUT Agent. Please check in the attachment.

As you can see I already tried to "name" the widget but unfortunately it didn't helped.
Could you please provide a solution/work around in this situation as application I'm testing has quite a few of those widgets.

Thank you in advance,
Michael
Comment 1 Alexandra Schladebeck CLA 2013-09-17 06:08:24 EDT
Thanks for the description. Could you clarify a couple of points? 

1. You said in the observation mode, but you mentioned a green border. Were you observing or performing object mapping? 
2. What toolkit are you testing? (Swing, SWT)
3. Is the current behaviour that a) the widget can be correctly addressed during an automated test, but the error occurs or b) the widget cannot be addressed during a test *and* the error occurs when clicking the widget in the observation / object mapping mode?

Thanks for the information.
Comment 2 Michael L CLA 2013-09-17 13:33:59 EDT
Hello Alexandra,

1. I'm sorry, I definitely was talking about the "Object Mapping Mode".
2. I'm testing RCP toolkit.
3. The answer is b): the widget cannot be addressed during a test *and* the error occurs when clicking the widget in the observation / object mapping mode?

Thanks,
Michael
Comment 3 Achim Loerke CLA 2013-09-23 04:42:02 EDT
@Team: Verify if the component is actually supported. The NPE should not be reported in either case.
Comment 4 Eclipse Genie CLA 2015-09-14 08:56:03 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Alexandra Schladebeck CLA 2015-09-17 10:10:15 EDT
Thanks Genie! Unfortunately, this issues hasn't been prioritised highly enough to make it into a sprint. My apologies for this. I'm assuming it's no longer relevant and closing as wontfix. If it is still relevant, please reopen.
Comment 6 Oliver Goetz CLA 2015-12-01 04:19:02 EST
Closed due to comment 5