Eclipse Community Forums: Jubula » Accessing custom widgets from Java API

Help

Home

Home » Archived » Jubula » Accessing custom widgets from Java API

Show: Today's Messages :: Show Polls :: Message Navigator

Accessing custom widgets from Java API [message #1684781]

Wed, 18 March 2015 15:22

Janine Kayser

Messages: 14
Registered: November 2012

Junior Member

Hi

I'm working on a Jubula Extension for Nebula Grid. Current state is that the extension works just fine using Jubula IDE or testexec.exe in combination with embedded AUT Agent and standalone AUT Agent.

The problem is that when using the Java API in combination with either embedded AUT Agent oder standalone AUT Agent the test steps testing the Nebula Grid widget fail with a "component not found" message. Test steps using standard widgets work just fine.

I have found instructions for using the Java API as well as on how to extend existing toolkits and managed both so far but now I m failing at the combination of both which seems not documented at all.

Can the Java API be used in combination with plugins supporting custom controls at all?
If that's the case what are the requirements?

Currently I manually create the CAPs and execute them.

final MessageCap messageCap = new MessageCap();
                messageCap.setMethod("rcSelect"); //$NON-NLS-1$
                messageCap.sethasDefaultMapping(false);
                messageCap.setCi((IComponentIdentifier) OM.Editor);
                Validate.notNull(SearchType.absolute, "Argument 'pathType' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(SearchType.absolute.rcValue(), "java.lang.String")); //$NON-NLS-1$
                Validate.notNull(0, "Argument 'preAscend' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(String.valueOf(0), "java.lang.Integer")); //$NON-NLS-1$
                Validate.notNull("Document/Name", "Argument 'textpath' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(String.valueOf("Quantitative Response Assay/Name"), "java.lang.String")); //$NON-NLS-1$
                Validate.notNull(Operator.equals, "Argument 'operator' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(Operator.equals.rcValue(), "java.lang.String")); //$NON-NLS-1$
                Validate.notNull(1, "Argument 'numberOfClicks' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(String.valueOf(1), "java.lang.Integer")); //$NON-NLS-1$
                Validate.notNull(InteractionMode.primary, "Argument 'mouseButton' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(InteractionMode.primary.rcValue(), "java.lang.Integer")); //$NON-NLS-1$
                Validate.notNull(BinaryChoice.no, "Argument 'extendSelection' must not be null"); //$NON-NLS-1$
                messageCap.addMessageParam(new MessageParam(BinaryChoice.no.rcValue(), "java.lang.String")); //$NON-NLS-1$
m_Aut.execute(messageCap, new Date());

Regards Janine

Report message to a moderator

Re: Accessing custom widgets from Java API [message #1684967 is a reply to message #1684781]

Wed, 18 March 2015 17:00

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Hi Janine,

It's great to hear that you're working with extensions! Unfortunately, they are not yet supported in the API, but this is something we're planning on working on in the near future. Feel free to put in an enhancement to track this in the bugzilla:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jubula

Then, when we work on it, you'll be kept up to date.

Hope that helps!
Alex

Report message to a moderator

Re: Accessing custom widgets from Java API [message #1686544 is a reply to message #1684967]

Thu, 19 March 2015 08:34

Janine Kayser

Messages: 14
Registered: November 2012

Junior Member

Hi Alex,

Thanks for the quick reply. Can you give me a rough estimate when this feature will be implemented (like 3 month, 1 year or 3 years). We are highly interested in writing our tests as J-Unit tests for including them into our build process. Is there a way to write tests in the ITE now and export them for use in the Java API as soon as the custom widget support is implemented for the API?

Regards Janine

Report message to a moderator

Re: Accessing custom widgets from Java API [message #1688152 is a reply to message #1686544]

Fri, 20 March 2015 08:31

Alexandra Schladebeck

Messages: 1613
Registered: July 2009

Senior Member

Hi Janine,

We're planning on looking into this in an upcoming sprint. The implementation time will depend to some degree on the mechanism we find / choose, but it's something I'd like to see available within the coming 3 months.
We do have a converter from ITE projects to API: there is some information on it in this thread:
https://www.eclipse.org/forums/index.php?t=msg&th=991013&goto=1619311&#msg_1619311

Hope that helps!
Alex

Report message to a moderator