[JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25093:
----------------------------------
Sprint: devex #141 December 2017 (was: devex #140 November 2017)
> IT: create tests for the Docker discovery feature
> -------------------------------------------------
>
> Key: JBIDE-25093
> URL: https://issues.jboss.org/browse/JBIDE-25093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Ondrej Dockal
> Labels: cdk, integration-test, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-09-22-17-35-34-902.png
>
>
> in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
> !image-2017-09-22-17-35-34-902.png!
> We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
> We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25093 at 11/22/17 6:21 AM:
-----------------------------------------------------------------
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Another case 1:
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url.
Another case 2:
Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (JBIDE-25014) - resolved
was (Author: odockal):
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Another case 1:
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url.
Another case 2:
Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (JBIDE-25014)
> IT: create tests for the Docker discovery feature
> -------------------------------------------------
>
> Key: JBIDE-25093
> URL: https://issues.jboss.org/browse/JBIDE-25093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Ondrej Dockal
> Labels: cdk, integration-test, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-09-22-17-35-34-902.png
>
>
> in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
> !image-2017-09-22-17-35-34-902.png!
> We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
> We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25375:
-------------------------------
Story Points: 10
Sprint: devex #141 December 2017
> Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25375
> URL: https://issues.jboss.org/browse/JBIDE-25375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM1
> Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
>
> {code:java}
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520
> java.version=1.8.0_144
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-25375:
----------------------------------
Assignee: Jeff MAURY
> Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25375
> URL: https://issues.jboss.org/browse/JBIDE-25375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM1
> Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
>
> {code:java}
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520
> java.version=1.8.0_144
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months