You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On http://www.saros-project.org/faq you can find a help text regarding the usage of Git and Saros together. The post mentions a Safe and Risky Layout. After a short manual test, I couldn't restore the problems with the Risky Layout. We should delete the wrong post, specify it more (maybe my test isn't handling everything) or keep in mind to not bring that post to the new website
Testcase: Add to Session a Project with Git
System under discussion: Eclipse with Saros Plugin
First Actor: Alice
Second Actor: Bob
Goal: Alice and Bob are in a shared session, same files on each side, both are at the same branch and commit
Requirements: Alice and Bob using Eclipse and are connected to Saros, Alice has an open project which uses Git, Alice's HEAD checkout at master, No files on Bob's side
Test: Alice shares every file (including the .git directory). Right and wrong folder structure
Expected Behaviour:
Right folder structure: .git directory isn't sent through Saros. Bob isn't using Git
Wrong folder structure: Saros send all the data. All goals reached.
After Test:
Right folder structure: Saros create a new project on Bob's side. Alice and Bob are in a shared session, same files on each side but .git the directory isn't sent through Saros. Bob isn't using Git. .gitignore file is sent through Saros
Wrong folder structure: Same as above
The text was updated successfully, but these errors were encountered:
The testcase above isn't reproducible. The Risky Layout is indeed risky. I've tried to reproduce it and realize that Bob received the .git directory.
I tested also the case when Bob had worked on the project before and because of that choose working with existing project in the invitation process. Same here. Bob's .git directory becomes updated by Alice's and this is risky, too.
My suggestions:
Create an stf test because it seems like the fact that I can't reproduce the testcase is a side effect of some changes in between this comment and the one 12 days ago and we need more control about things like that.
Keep the Risky and Safe Layout-Post on the FAQ side and
On
http://www.saros-project.org/faq
you can find a help text regarding the usage of Git and Saros together. The post mentions a Safe and Risky Layout. After a short manual test, I couldn't restore the problems with the Risky Layout. We should delete the wrong post, specify it more (maybe my test isn't handling everything) or keep in mind to not bring that post to the new websiteTestcase: Add to Session a Project with Git
System under discussion: Eclipse with Saros Plugin
First Actor: Alice
Second Actor: Bob
Goal: Alice and Bob are in a shared session, same files on each side, both are at the same branch and commit
Requirements: Alice and Bob using Eclipse and are connected to Saros, Alice has an open project which uses Git, Alice's HEAD checkout at master, No files on Bob's side
Test: Alice shares every file (including the .git directory). Right and wrong folder structure
Expected Behaviour:
Right folder structure: .git directory isn't sent through Saros. Bob isn't using Git
Wrong folder structure: Saros send all the data. All goals reached.
After Test:
Right folder structure: Saros create a new project on Bob's side. Alice and Bob are in a shared session, same files on each side but .git the directory isn't sent through Saros. Bob isn't using Git. .gitignore file is sent through Saros
Wrong folder structure: Same as above
The text was updated successfully, but these errors were encountered: