1. ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location
2. EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid
   (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc)
3. EXEC: launch connection wizard
4. EXEC: provide server url and authentication means
5. ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area
   

Result:
You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more.

Expected result:
Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there.