[
https://issues.jboss.org/browse/JBIDE-25378?page=com.atlassian.jira.plugi...
]
Ondrej Dockal edited comment on JBIDE-25378 at 2/13/18 4:36 AM:
----------------------------------------------------------------
Verification steps:
Use case 1: CDK 3.2+ Server Adapter can be operated (covered by
o.j.t.cdk.ui.bot.test.CDK32IntegrationTest)
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded,
'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
Use case 2: CDK 3.2+ Server Adapter can operate another profile
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded,
'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with profile set to value different than
"minishift"
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded,
'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Create New CDK 3.2+ server with profile set to value different than
"minishift"
4. EXEC: Start default server adapter with default profile
5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
7. EXEC: Start server adapter with named profile set
8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
10. EXEC: Stop named profile
11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli),
SA state is stopped
12. EXEC: Stop default profile
13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli),
SA state is stopped
was (Author: odockal):
Verification steps:
Use case 1: CDK 3.2+ Server Adapter can be operated
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded,
'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
Use case 2: CDK 3.2+ Server Adapter can operate another profile
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded,
'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with profile set to value different than
"minishift"
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded,
'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Create New CDK 3.2+ server with profile set to value different than
"minishift"
4. EXEC: Start default server adapter with default profile
5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
7. EXEC: Start server adapter with named profile set
8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker
connection was created, SA state is started (stopped)
10. EXEC: Stop named profile
11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli),
SA state is stopped
12. EXEC: Stop default profile
13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli),
SA state is stopped
Add cdk itests for multiple server adapters using minishift profile
feature
---------------------------------------------------------------------------
Key: JBIDE-25378
URL:
https://issues.jboss.org/browse/JBIDE-25378
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: integration-tests
Affects Versions: 4.5.1.Final
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Priority: Critical
Labels: cdk, cdk_server_adapter
Fix For: 4.5.3.AM1
Implement base scenarios for CDK 3.2+ server adapter's profile feature that would
include work with two server adapters.
https://docs.openshift.org/latest/minishift/using/profiles.html
Test cases can be derived from
https://issues.jboss.org/browse/JBIDE-25055. This jira
will cover 2nd and 3rd use case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)