[jbosstools-issues] [JBoss JIRA] (JBIDE-24125) Import wizard: adapt ITs to changes introduced in JBIDE-24048
[
https://issues.jboss.org/browse/JBIDE-24125?page=com.atlassian.jira.plugi...
]
Radim Hopp commented on JBIDE-24125:
------------------------------------
We have 4 cases that should be covered by tests:
* there's a folder with the name of the clone but it's no git repo
* there's a folder with the name of the clone, it's a git folder but remote is not
pointing to the same source, so it looks like it's not the right source
* there's a folder with the same name as the clone, it's a git repo but
there's no remote at all, looks like it's not the right source
* there's a folder with the same name, it's a git repo, it points to the same
source as what's being built in OpenShift, but the branch that we want to check does
not exist yet
Import wizard: adapt ITs to changes introduced in JBIDE-24048
-------------------------------------------------------------
Key: JBIDE-24125
URL: https://issues.jboss.org/browse/JBIDE-24125
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.4.AM2
Reporter: Andre Dietisheim
Assignee: Radim Hopp
In JBIDE-24048 changes have been done to the import wizard. We should change the ITs to
cover these changes.
@rhopp @bdshadow can you please test this since it's a rather larger change and
provides changes in how it behaves?
* Validations were extended:
** is the existing clone destination a git repo?
** is the existing clone destination a clone of the source that is used in OpenShift?
* We now also ask the user if he wants to checkout the correct branch (the one that's
used in OpenShift) in the existing git repo
* UI was slightly changed according to requests made in JBIDE-21935
* We now also close the wizard dialog before executing the import. This should allow the
user to continue working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)