[jbosstools-issues] [JBoss JIRA] (JBTIS-652) Adapt SAP tests according to the changes made in new Camel editor

Andrej Podhradsky (JIRA) issues at jboss.org
Tue Apr 12 07:53:00 EDT 2016


    [ https://issues.jboss.org/browse/JBTIS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190468#comment-13190468 ] 

Andrej Podhradsky commented on JBTIS-652:
-----------------------------------------

Also the doOperation is not supported anymore

> Adapt SAP tests according to the changes made in new Camel editor
> -----------------------------------------------------------------
>
>                 Key: JBTIS-652
>                 URL: https://issues.jboss.org/browse/JBTIS-652
>             Project: JBoss Tools Integration Stack
>          Issue Type: Task
>          Components: Fuse IDE, QE
>    Affects Versions: 9.0.0.CR1
>            Reporter: Andrej Podhradsky
>            Assignee: Andrej Podhradsky
>
> I'm still getting the following NPE when I try to add a component to the route
> {code}
> java.lang.NullPointerException
> 	at org.jboss.reddeer.gef.handler.EditPartHandler.getFigure(EditPartHandler.java:83)
> 	at org.jboss.reddeer.gef.impl.editpart.AbstractEditPart.getFigure(AbstractEditPart.java:89)
> 	at org.jboss.tools.fuse.reddeer.editor.CamelComponentEditPart.getBounds(CamelComponentEditPart.java:22)
> 	at org.jboss.tools.fuse.reddeer.editor.CamelEditor.getInEditorCoords(CamelEditor.java:608)
> 	at org.jboss.tools.fuse.reddeer.editor.CamelEditor.addCamelComponent(CamelEditor.java:150)
> 	at org.jboss.tools.fuse.ui.bot.test.SAPComponentTest.testSAPTRFCServer(SAPComponentTest.java:194)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunTestMethod.evaluate(RunTestMethod.java:36)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeTestExtensions.evaluate(RunIBeforeTestExtensions.java:63)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:51)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> 	at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> 	at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> 	at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34)
> 	at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146)
> 	at org.junit.runners.Suite.runChild(Suite.java:128)
> 	at org.junit.runners.Suite.runChild(Suite.java:27)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.junit.runners.Suite.runChild(Suite.java:128)
> 	at org.junit.runners.Suite.runChild(Suite.java:27)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> 	at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58)
> 	at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:115)
> 	at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> 	at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list