[JBoss JIRA] (JBTIS-1206) Test SwitchYardEditorValidatorsTest is sometimes failing
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1206?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBTIS-1206.
------------------------------------
> Test SwitchYardEditorValidatorsTest is sometimes failing
> --------------------------------------------------------
>
> Key: JBTIS-1206
> URL: https://issues.jboss.org/browse/JBTIS-1206
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE, switchyard
> Affects Versions: 4.2.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.5.2.Final
>
>
> *Error Message*
> {code}
> Menu item 'Save' is not enabled
> {code}
> *Stacktrace*
> {code}
> org.eclipse.reddeer.workbench.exception.WorkbenchLayerException: Menu item 'Save' is not enabled
> at org.eclipse.reddeer.workbench.impl.editor.AbstractEditor.save(AbstractEditor.java:132)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.doSave(SwitchYardEditor.java:286)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.access$0(SwitchYardEditor.java:272)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor$EditorIsSaved.test(SwitchYardEditor.java:315)
> at org.eclipse.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:102)
> at org.eclipse.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:146)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:131)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:96)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:63)
> at org.eclipse.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:49)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.save(SwitchYardEditor.java:303)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorValidatorsTest.validatorDTDTest(SwitchYardEditorValidatorsTest.java:78)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBTIS-1206) Test SwitchYardEditorValidatorsTest is sometimes failing
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1206?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1206:
-------------------------------------
Affects Version/s: 4.2.0.Final
(was: 4.2.0.Final-TP)
> Test SwitchYardEditorValidatorsTest is sometimes failing
> --------------------------------------------------------
>
> Key: JBTIS-1206
> URL: https://issues.jboss.org/browse/JBTIS-1206
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE, switchyard
> Affects Versions: 4.2.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.5.2.Final
>
>
> *Error Message*
> {code}
> Menu item 'Save' is not enabled
> {code}
> *Stacktrace*
> {code}
> org.eclipse.reddeer.workbench.exception.WorkbenchLayerException: Menu item 'Save' is not enabled
> at org.eclipse.reddeer.workbench.impl.editor.AbstractEditor.save(AbstractEditor.java:132)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.doSave(SwitchYardEditor.java:286)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.access$0(SwitchYardEditor.java:272)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor$EditorIsSaved.test(SwitchYardEditor.java:315)
> at org.eclipse.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:102)
> at org.eclipse.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:146)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:131)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:96)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:63)
> at org.eclipse.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:49)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.save(SwitchYardEditor.java:303)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorValidatorsTest.validatorDTDTest(SwitchYardEditorValidatorsTest.java:78)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBTIS-874) Test 'addDroolsImplementationWithNewJavaInterfaceTest' sometimes fails
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-874?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-874.
-----------------------------------
> Test 'addDroolsImplementationWithNewJavaInterfaceTest' sometimes fails
> ----------------------------------------------------------------------
>
> Key: JBTIS-874
> URL: https://issues.jboss.org/browse/JBTIS-874
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE, switchyard
> Affects Versions: 4.3.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.2.0.Final-TP
>
> Attachments: org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest.png
>
>
> Error Message
> Timeout after: 60 s.: an item matching Matcher matching text to regular expression '.*AgendaStats.*' in
> SwitchYardServiceChannel - org.switchyard.component.common.knowledge.service
> Stacktrace
> {code}
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: an item matching Matcher matching text to regular expression '.*AgendaStats.*' in
> SwitchYardServiceChannel - org.switchyard.component.common.knowledge.service
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addClass(ImplementationKnowledgePage.java:165)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addItem(ImplementationKnowledgePage.java:144)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addListener(ImplementationKnowledgePage.java:99)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkAdvancedProperties(SwitchYardEditorImplementationsTest.java:792)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkDroolsAdvancedProperties(SwitchYardEditorImplementationsTest.java:782)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest(SwitchYardEditorImplementationsTest.java:471)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBTIS-1206) Test SwitchYardEditorValidatorsTest is sometimes failing
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1206?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1206:
-------------------------------------
Fix Version/s: 4.5.2.Final
(was: 4.2.0.Final-TP)
> Test SwitchYardEditorValidatorsTest is sometimes failing
> --------------------------------------------------------
>
> Key: JBTIS-1206
> URL: https://issues.jboss.org/browse/JBTIS-1206
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE, switchyard
> Affects Versions: 4.2.0.Final-TP
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.5.2.Final
>
>
> *Error Message*
> {code}
> Menu item 'Save' is not enabled
> {code}
> *Stacktrace*
> {code}
> org.eclipse.reddeer.workbench.exception.WorkbenchLayerException: Menu item 'Save' is not enabled
> at org.eclipse.reddeer.workbench.impl.editor.AbstractEditor.save(AbstractEditor.java:132)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.doSave(SwitchYardEditor.java:286)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.access$0(SwitchYardEditor.java:272)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor$EditorIsSaved.test(SwitchYardEditor.java:315)
> at org.eclipse.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:102)
> at org.eclipse.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:146)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:131)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:96)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:63)
> at org.eclipse.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:49)
> at org.jboss.tools.switchyard.reddeer.editor.SwitchYardEditor.save(SwitchYardEditor.java:303)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorValidatorsTest.validatorDTDTest(SwitchYardEditorValidatorsTest.java:78)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25814:
------------------------------------------
To infer a connection from a resource one can simply call
{code}
ConnectionsRegistryUtil#getConnectionFor(resource)
{code}
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: server_adapter_wizard
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25814 at 3/14/18 10:34 AM:
--------------------------------------------------------------------
To infer a connection from a resource one can simply call
{code}
ConnectionsRegistryUtil.getConnectionFor(resource)
{code}
was (Author: adietish):
To infer a connection from a resource one can simply call
{code}
ConnectionsRegistryUtil#getConnectionFor(resource)
{code}
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: server_adapter_wizard
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25814:
-------------------------------------
Description:
steps:
# ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
# EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
# ASSERT: Connection selection page pops up
# EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
# EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
# ASSERT: Connection selection page pops up
Result:
the connection selection page has the 1st connection selected, not the one that we used most recently.
(If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
was:
steps:
# ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
# EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
# ASSERT: Connection selection page pops up
# EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
# EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
# ASSERT: Connection selection page pops up
Result:
the connection selection page has the 1st connection selected, not the one that we used most recently.
(If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: server_adapter_wizard
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years