TC 8.2 + SVN (PushOK or TamTam)
Having some issues with TC 8.2 source control. We have a setup where we're using svn (We don't have much of a choice here). We've used PushOK, as well as TamTam. Nothing works the way it should.
We *might* be able to get an initial check in to complete, but there are always issues - for example, adding a keyword test fails ("Catastrophic failure" per TamTam, or "The file was not added to source control" from PushOK -- really useful, complete, and verbose errors to work with here...). This happens even if no one uses the repo and we check out an entire project first (Which sometimes even THAT fails).
We also have not figured out how to set up TC with source control on a new machine -- for example, we have a project on the repo, and we set up a new PC for a new engineer. In order to get the repo on his machine through test complete seems impossible since creating a test suite and adding it to source control will overwrite project files on the repo with useless ones. What we have done is use TortoiseSVN to bring down the current revision and then load TC up and add it to source control. That seems to kind-of work, but not really, since we still get all kinds of errors when actually interacting with the repo.
None of our developers have had issues with our repo for 5+ years, so I don't think thats the problem. I think the issue lies solely with TC, or solely with something we are doing wrong. Since there are really no clear guides on how to set this up, we're kinda flying blind here.
Any advice would be most appreciated.
Thanks.
We *might* be able to get an initial check in to complete, but there are always issues - for example, adding a keyword test fails ("Catastrophic failure" per TamTam, or "The file was not added to source control" from PushOK -- really useful, complete, and verbose errors to work with here...). This happens even if no one uses the repo and we check out an entire project first (Which sometimes even THAT fails).
We also have not figured out how to set up TC with source control on a new machine -- for example, we have a project on the repo, and we set up a new PC for a new engineer. In order to get the repo on his machine through test complete seems impossible since creating a test suite and adding it to source control will overwrite project files on the repo with useless ones. What we have done is use TortoiseSVN to bring down the current revision and then load TC up and add it to source control. That seems to kind-of work, but not really, since we still get all kinds of errors when actually interacting with the repo.
None of our developers have had issues with our repo for 5+ years, so I don't think thats the problem. I think the issue lies solely with TC, or solely with something we are doing wrong. Since there are really no clear guides on how to set this up, we're kinda flying blind here.
Any advice would be most appreciated.
Thanks.
