[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-718: ------------------------------------ The basic use case is: 1) Create a CDK server adapter, pointing to the folder with the Vagrantfile from cdk installation. If from installer, this folder should have a .cdk file 2) right-click server adapter and select 'start'. this should run vagrant up, and start the server 3) credentials chosen in new server wizard should be passed to vagrant up command via environment variables, so vagrant up should succeed 4) Once started, a new connection in Docker Explorer should be added if it didn't exist yet. 5) Once started, a new connection in OpenShift Explorer should be added if it didn't exist yet. 6) These two connections should 'work'. ie, if you expand them, the proper elements should be where they belong 7) right-click server and select 'stop' should run vagrant halt 8) repeated start / stop commands shouldn't break This may sound simple, but much of the work was focussed on the openshift repository, so the rest of the usecases all involve openshift workflows. Once you have an openshift connection, you should be able to create an application, a project, whether node.js or eap, from the templates. This should clone some remote git repo, import a project into the workspace, and begin building the app on the openshift instance. Once the app is created and built, you should be able to turn the openshift app into its own server adapter by right-clicking the openshift app and selecting "Server Adapter..." I believe Martin may have a more in-depth test plan available for both the CDK and OpenShift instances, or can help you find it. Martin? -- This message was sent by Atlassian JIRA (v6.4.11#64026)