[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 commented on JBIDE-25093:
---------------------------------------
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
> 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, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25049.
---------------------------------
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: discover_openshift_registry.png, screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25049:
---------------------------------------
[~adietish] I have followed your steps, I got rid of the service docker-regisrty in started minishift via command line, and I got this dialog when trying to Discover image registry url:
!discover_openshift_registry.png|thumbnail!
which seems alright to me.
Verified on devstudio 11.1.0.AM3-v20171005-1232-B1225.
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: discover_openshift_registry.png, screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25049:
----------------------------------
Attachment: (was: discover_openshift_registry.png)
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: discover_openshift_registry.png, screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25049:
----------------------------------
Attachment: discover_openshift_registry.png
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: discover_openshift_registry.png, screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25049:
----------------------------------
Attachment: discover_openshift_registry.png
> Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25049
> URL: https://issues.jboss.org/browse/JBIDE-25049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.1.AM3
>
> Attachments: discover_openshift_registry.png, screenshot-1.png
>
>
> # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry.
> {code}
> [adietish@localhost minishift]$ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> You can achieve that by :
> * have server adapter stopped, minishift started
> * logging into your cdk with oc as "admin" and then:
> {code}
> oc project default
> oc delete svc docker-registry
> {code}
> Once the service is deleted you need to start the cdk.
> # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
> # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
> # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
> # EXEC: edit the OpenShift connection
> # ASSERT: connection wizard shows up
> # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
> # EXEC: hit "Discover"
> Result
> An error dialog shows up telling you no registry provider could be found
> !screenshot-1.png!
>
> the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months