I started a TS project (e.g. 'Foo') with a few test cases and successfully connected to an empty remote GitHub repository(e.g. githubURL/<company>/bar). As the single contributor so far to this project, I am able to commit and push additional test cases to the remote repository and re-launch TS to continue my work.
What would you recommend as a workflow for sharing this remote project for other QA members to see this project where they also will be adding test cases and eventually the team would be able to pull the latest, commit their changes and push these changes for others to do the same? Maybe questions would help narrow down some answers:
1) Should other QA members "Open" this remote project, or should they "Create" a new project and "Connect" to the remote repository, then "Pull"
2) What is the difference between opening a remote project versus creating a project and connecting to a remote?
Without getting too deep into our issues, when opening a remote project (that is stable from my desktop and usage is fine), other QA members are getting one of several errors(e.g. 401 errors, error in deserializing object, non-fastforwardable, etc).
3 Answers, 1 is accepted
Thank you for your interest in Telerik Test Studio.
The option 'Open' performs git clone and should be used when opening an existing remote repository for first time. This will create a local copy of the remote repository. Here you could read further.
On the other hand 'Connect' options perform git pull at first to sync the tracking of the master branch and then git push to update all changes to the newly created remote repository. So in the case when a new local project needs to be added to git you should use connect. Please find details here.
I hope this will be useful to you. Let me know in case of further questions please. Thanks!
Regards,
Elena Tsvetkova
Telerik by Progress
Rank 1
Thank you for your interest in Telerik Test Studio.
The option 'Open' performs git clone and should be used when opening an existing remote repository for first time. This will create a local copy of the remote repository. Here you could read further.
On the other hand 'Connect' options perform git pull at first to sync the tracking of the master branch and then git push to update all changes to the newly created remote repository. So in the case when a new local project needs to be added to git you should use connect. Please find details here.
I hope this will be useful to you. Let me know in case of further questions please. Thanks!
-----------------
Thank you for your response. It confirmed also what we found when using 'connect'.
We ended up abandoning Test Studio's Git interface as the results of multiple people sharing was unpredictable and failing too often (401 errors with Open, Error deserializing object, status:NonFastForwardable, ...). Open to a remote repository would 90% be unsuccessful with these errors, and we resorted to the incorrect usage of "Connect" with an existing repository, regardless of the instructions in the User Guide. The behind-the-scenes Push with connect is what caused us very unpredictable results.
We are using command line git commands to accomplish --- and control --- what and how we share amongst the team and it is working smoothly now. I have become quite adept at deciphering the log files and examining what entries in Settings.aiis is causing problems. We have a process where the Settings.aiis file is never pushed by anyone else unless reviewed.
Thank you for getting back to me. I am glad to hear you have found an approach working smoothly for you although it is not the one provided by Test Studio.
I hope you will be working flawlessly from now on. However do not hesitate to contact Telerik Support Team again in case of further difficulties.
Regards,
Elena Tsvetkova
Telerik by Progress