[jbosstools-issues] [JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature

[Ondrej Dockal (JIRA)]

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

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)